TELCODOCS#2637: Adding custom MCP upgrade content#111682
Conversation
openshift-ci
Bot
added
the
size/L
|
🤖 Thu May 14 17:38:07 - Prow CI generated the docs preview: |
|
|
||
| :_mod-docs-content-type: PROCEDURE | ||
| [id="configuring-custom-machine-config-pools-parallel-upgrades_{context}"] | ||
| = Configuring custom machine config pools for parallel upgrades |
There was a problem hiding this comment.
🤖 [error] AsciiDocDITA.ShortDescription: Assign [role="_abstract"] to a paragraph to use it as in DITA.
|
|
||
| You can accelerate upgrades in large clusters by partitioning worker nodes into custom Machine Config Pools (MCPs) that align with Kubernetes failure domains (KFDs). This approach changes the default sequential node-by-node update process into a parallel partition-based strategy. | ||
|
|
||
| This strategy is particularly relevant for bare-metal and on-premise environments where you cannot add temporary surge capacity during upgrades. By updating all nodes in a single failure domain simultaneously, you can reduce upgrade time while keeping other failure domains available to maintain High Availability (HA) for workloads. |
There was a problem hiding this comment.
🤖 [error] RedHat.TermsErrors: Use 'bare metal' rather than 'bare-metal'. For more information, see RedHat.TermsErrors.
|
@sr1kar99: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
|
@r3v5 |
|
|
||
| * *nodeSelector*: Define a label to identify the nodes that belong to this pool (for example, `node-role.kubernetes.io/worker-0`). | ||
|
|
||
| . Apply the `topology.kubernetes.io/zone` label to identify the KFD for the Kubernetes scheduler, and the custom node role label (for example, `worker-0`) to assign the node to the MCP by running the following command: |
There was a problem hiding this comment.
Apply the.... to identify each KFD for the Kubernetes scheduler.
Looks like only one topology label needs to be added, but a different one must be added to each MCP (worker-0, worker-1, worker-2, worker-3..).
4 participants
Version(s):
4.21+
Issue:
https://redhat.atlassian.net/browse/TELCODOCS-2607
Link to docs preview:
QE review: