docs: clarify Global DR network requirements - #969
Merged
Conversation
Deploying alauda-container-platform with
|
| Latest commit: |
5b77d3a
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://c025bf9c.alauda-container-platform.pages.dev |
| Branch Preview URL: | https://chao-ait-72814-global-dr-net.alauda-container-platform.pages.dev |
chinameok
added a commit
that referenced
this pull request
Jul 20, 2026
* docs: clarify Global DR network requirements * docs: use official etcd Synchronizer terminology * docs: link DR network requirements from prerequisites --------- (cherry picked from commit fe47e36) Co-authored-by: Chao Zhou <chaozhou@alauda.io>
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
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.
What changed
Why
The platform domain normally resolves only to the Primary Cluster, so steady-state traffic is normally initiated from Standby to Primary. A failover swaps the cluster roles and reverses the required connection direction. The existing documentation listed the ports but did not explain this bidirectional network prerequisite, which could lead to a one-way configuration that fails after switchover. The cross-reference ensures that users configuring general load balancer rules discover the complete Global DR requirements before installation.
Where to backport
This PR targets master only. Do not backport yet. After the master PR is reviewed and merged, backport to applicable release branches only after separate authorization from Chao.
Validation
Review level
Technical correctness and customer-operable Global DR network prerequisites.