Skip to content

Update KCP node provisioning details in documentation #4299

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
deepukraju wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update KCP node provisioning details in documentation #4299

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions operator-nexus/concepts-cluster-deployment-overview.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -67,6 +67,11 @@ The ephemeral bootstrap node sequentially provisions each KCP node, and if a KCP

Once KCP nodes are successfully provisioned, the deployment action proceeds to provision NMP nodes in parallel. Each management group must achieve at least a 50% provisioning success rate. If this requirement isn't met, the cluster deployment action fails, resulting in the cluster status being marked as failed.

> [!NOTE]
> The availability of spare KCP node on the cluster depends on the 'EnableRepurposeSpareKcpNode' feature flag. If the feature is enabled there will be no spare KCP on the cluster and it will be provisoined as a NMP node.
> - The required number of KCP nodes is always maintained in the cluster.
> - This feature is available for runtime version 4.11 and above.

Upon successful provisioning of NMP nodes, up to two storage appliances are created before the deployment action proceeds with provisioning the compute nodes. Compute nodes are provisioned in parallel, and once the defined compute node threshold is met, the cluster status transitions from Deploying to Running. However, the remaining nodes continue undergoing the provisioning process until they too are successfully provisioned.


Expand Down