-
Epic
-
Resolution: Unresolved
-
Major
-
None
-
None
-
None
-
Ability to set priority to the MachineConfigs
-
True
-
False
-
To Do
-
0
-
0
- What is the nature and description of the request?
As per https://bugzilla.redhat.com/show_bug.cgi?id=1965556 . The foundational issue here is that custom pools always inherit from worker pool machine configuration, meaning that if you want to have a kubeletconfig for the base worker pool and a different one for a custom pool, the custom pool machineconfig selector will make it have both kubeletconfig-generated-machineconfigs, and those are conflicting.
In my customer's env, there are some nodes with two MCPs. One is the worker and the other is a name with lower alphanumeric order than 'worker', such as 'custom', 'upf', etc. when they want to apply a new kubeletconfig for the second pool, the newly created MC never rolls out which is by desinged.
So the customer requested a RFE because they need some features that are able to set the 'priority' to the kubeletconfigcontroller or some components related to MCP, so that we can control the order of the MC in a more flexiable way. - Why does the customer need this? (List the business requirements here)
As the customer has a large number of worker nodes, they would also have many different MCPs in addition to the worker, so they need a more flexable way to manage MCPs and kubeletconfigs.
In the customer's env, some particular worker nodes need to have the second MCP label to apply an additional kubeletconfig. when the basic worker pool has been applied a kubeletconfig, in order to make sure the second kubeletconfig is able to be applied with a newly created MC without problems, the customer should take more care of naming the second MCP to meet the current MCO working logic. The customer wants to manage the MC not only in the alphanumeric order, but also in a 'priority' order which can be controlled by the user.
- relates to
-
-
- New
-
- links to
There are no Sub-Tasks for this issue.
