docs: add failure domain guide for CAPV#6
Open
jiazhiguang wants to merge 1 commit into
Open
Conversation
Document vSphere failure domain concepts, topology models, and deployment zone relationships in CAPV. Explain how VSphereMachineConfigPool works alongside failure domains to provide stable node identity and placement guidance. Clarify that the slot-availability filter is cluster-aware (Datacenter-aggregated), not pool-aware: when only some failure domains run out of slots they are excluded; when all are exhausted CAPV keeps reporting them and surfaces the state via FailureDomainsAvailable=False so new Machines may still fail until capacity is restored. Mark cross-Datacenter as an advanced scenario rather than the default, listing the network / VIP / template / datastore / CPI/CSI prerequisites that must be met before it can be used. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. 🗂️ Base branches to auto review (3)
Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
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.
Document vSphere failure domain concepts, topology models, and deployment zone relationships in CAPV.
Explain how VSphereMachineConfigPool works alongside failure domains to provide stable node identity and placement guidance.
Clarify that the slot-availability filter is cluster-aware (Datacenter-aggregated), not pool-aware: when only some failure domains run out of slots they are excluded; when all are exhausted CAPV keeps reporting them and surfaces the state via FailureDomainsAvailable=False so new Machines may still fail until capacity is restored.
Mark cross-Datacenter as an advanced scenario rather than the default, listing the network / VIP / template / datastore / CPI/CSI prerequisites that must be met before it can be used.