Update KCP node provisioning details in documentation#4299
Conversation
Clarified the behavior of the 'EnableRepurposeSpareKcpNode' feature flag and its impact on KCP node availability. Added notes on KCP node maintenance and runtime version requirements.
|
@deepukraju : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
|
Learn Build status updates of commit 0ce8483: ✅ Validation status: passed
For more details, please refer to the build report. |
|
Can you review the proposed changes? IMPORTANT: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
prmerger-automator
Bot
added
the
aq-pr-triaged
There was a problem hiding this comment.
Pull request overview
Adds a note in the Operator Nexus cluster deployment overview documentation describing how the EnableRepurposeSpareKcpNode feature flag affects spare KCP node provisioning, along with statements that the required number of KCP nodes is always maintained and that the feature requires runtime version 4.11+.
Changes:
- Add a
[!NOTE]block explaining theEnableRepurposeSpareKcpNodefeature flag behavior. - Document that the required number of KCP nodes is always maintained.
- Document the 4.11+ runtime version requirement for the feature.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| 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. |
| 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. |
Clarified the behavior of the 'EnableRepurposeSpareKcpNode' feature flag and its impact on KCP node availability. Added notes on KCP node maintenance and runtime version requirements.