-
Feature
-
Resolution: Done
-
Major
-
None
Feature Overview (aka. Goal Summary)
The MCO merges MachineConfigs in alphanumerical order. Because all custom pools also are workers, this effectively means that all "worker" configs will take precedence over custom pools that come earlier in alphabetic order. This is counter to most expectations where the reason for creating the custom pool is in order to be different than the worker pool.
Goals (aka. expected user outcomes)
Custom pool configs will "win" over worker configs. This is inline with what most customers expect.
[original description related to a specific scenario that this more general feature will help facilitate. It's been moved to comments]
- is blocked by
-
MCO-641 Clarity in Custom Config Application
- Closed
- is duplicated by
-
OCPSTRAT-825 Priority Order Change for merging MachineConfigs
- Closed
- is related to
-
MCO-639 create a priority order for MC merging
- To Do
- relates to
-
RFE-2846 Hive managed customizations for Machine Configuration Operator to configure High PID and THP Support
- Under Review