test(gcp): end-to-end multi-data-center bootstrap coverage and docs - #632
Open
NJona wants to merge 3 commits into
Open
test(gcp): end-to-end multi-data-center bootstrap coverage and docs#632NJona wants to merge 3 commits into
NJona wants to merge 3 commits into
Conversation
NJona
force-pushed
the
multi-dc-10-multi-dc-tests-docs
branch
from
August 4, 2026 08:12
5445fdf to
f244cdb
Compare
NJona
force-pushed
the
multi-dc-10-multi-dc-tests-docs
branch
from
August 5, 2026 15:48
3158c62 to
5a9f70e
Compare
NJona
force-pushed
the
multi-dc-10-multi-dc-tests-docs
branch
2 times, most recently
from
August 10, 2026 14:16
cc56549 to
4afb77e
Compare
NJona
force-pushed
the
multi-dc-10-multi-dc-tests-docs
branch
2 times, most recently
from
August 12, 2026 09:16
8ed3f15 to
d97200b
Compare
Covers a full --multi-dc bootstrap in one spec: two data centers with their own nodes, IPs, configs and vaults, the second one pointed at the first's PostgreSQL server, both told about the topology, and the secrets partitioned the way a shared database and separate clusters require. This is the test that pins the invariants the individual commits only enforce locally. Also documents multi-DC on GCP in the installation guide: the quota footprint, the install order, the two config/vault/secrets-dir paths, the topology keys and the DNS scheme, including the per-data-center platform records the frontend depends on. 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>
NJona
force-pushed
the
multi-dc-10-multi-dc-tests-docs
branch
from
August 13, 2026 12:48
b9e4dd5 to
e49aade
Compare
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.
Covers a full
--multi-dcbootstrap in one spec: two data centers with their own nodes, IPs, configs and vaults, the second one pointed at the first's PostgreSQL server, both told about the topology, and the secrets partitioned the way a shared database and separate clusters require. This is the test that pins the invariants the individual PRs only enforce locally.Also documents multi-DC on GCP in the installation guide: the quota footprint, the install order, the two config/vault/secrets-dir paths, the topology keys, and the DNS scheme including the per-data-center platform records the frontend depends on.
Review notes
Test and documentation only.
Part of the
oms beta bootstrap-gcp --multi-dcstack (10 PRs). Merge in order; each PR is based on its predecessor.