feat(gcp): configure hosts, gateways and installs per data center - #627
Open
NJona wants to merge 3 commits into
Open
feat(gcp): configure hosts, gateways and installs per data center#627NJona wants to merge 3 commits into
NJona wants to merge 3 commits into
Conversation
Migrates the infrastructure steps from the single implicit data center to the layout: root login and host configuration run over every data center's nodes, each data center reserves its own gateway, public gateway and SSH proxy IP under a suffixed name, and each gets its own k0s configuration script patching its own gateway services. InstallCodesphere and RunK0sConfigScript now loop over the data centers in ascending order and log a step per data center. The order matters once there is more than one: the primary data center's install creates the database, roles and schema the others reuse, and a k0s script can only patch gateway services an install has already created. The install command moves into the exported InstallCommand, since the CLI prints it for the operator when the bootstrap does not install itself, and it now names the data center's own config, vault and age key. EnsureHostsConfigured also creates /etc/codesphere/secrets up front on every node: the installer uploads a data center's age key to that fixed path but only creates its own configured secrets.baseDir, so for a data center whose baseDir differs the upload target would not exist. Behaviour for a single data center is unchanged — same VM names, same IP names, same script, same install command. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Signed-off-by: Jona Neef <Jona.Neef.97@gmail.com>
Signed-off-by: NJona <25478046+NJona@users.noreply.github.com>
Signed-off-by: NJona <25478046+NJona@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Migrates the infrastructure steps from the single implicit data center to the layout: root login and host configuration run over every data center's nodes, each data center reserves its own gateway, public gateway and SSH proxy IP under a suffixed name, and each gets its own k0s configuration script patching its own gateway services.
InstallCodesphereandRunK0sConfigScriptloop over the data centers in ascending order and log a step per data center. The order matters once there is more than one: the primary's install creates the database, roles and schema the others reuse, and a k0s script can only patch gateway services an install has already created.The install command moves into the exported
InstallCommand, since the CLI prints it for the operator when the bootstrap does not install itself, and it now names the data center's own config, vault and age key.Review notes
EnsureHostsConfiguredalso creates/etc/codesphere/secretsup front on every node: the installer uploads a data center's age key to that fixed path but only creates its own configuredsecrets.baseDir, so for a data center whosebaseDirdiffers the upload target would not exist. Harmless, since nodes belong to exactly one data center.Behaviour for a single data center is unchanged — same VM names, same IP names, same script, same install command.
Part of the
oms beta bootstrap-gcp --multi-dcstack (10 PRs). Merge in order; each PR is based on its predecessor.