-
Feature Request
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
None
-
None
-
Product / Portfolio Work
-
None
-
False
-
-
None
-
None
-
None
-
-
None
-
None
-
None
-
None
-
None
1. Proposed title of this feature request
Separate Administrator Config rollout from Cluster Upgrade config changes in standalone clusters
2. What is the nature and description of the request?
For operational reasons, the client would like to be able to pause MCP upgrades to accommodate allowable maintenance windows. These pauses could be staged so they only do a portion of the cluster nodes per-window, so this might take some time. During this period, they require the ability to have other machineConfig changes be made on these pools.
3. Why does the customer need this? (List the business requirements here)
Node reboots are impactful for some workloads, so these have to be scheduled to fit into defined maintenance windows. Given this, they have to pause the MCP upgrade rollouts and might require several windows to be able to complete an upgrade. During this period, they require the ability to be able to manage these pools and make changes to the deployed machineconfigs.
4. List any affected packages or components.
MCO