1. Proposed title of this feature request

Allow creation of infra nodes without the worker label

2. What is the nature and description of the request

Remove the worker label from extra nodes we add to the cluster. When a new node is added to the cluster, it initially joins with the worker role and is therefore managed by the worker MachineConfigPool. As a result, the worker MachineConfigs are applied first. Once the node is relabeled with the infra role, it is reassigned to the infra MachineConfigPool, and the infra-specific MachineConfigs are then applied.

3. Why does the customer need this? (List the business requirements here)

The customer wants to configure system-reserved settings for different node types:

Worker nodes have 1.4 TB of RAM and require a kubelet reservation of approximately 119 GB of memory.

Infrastructure nodes have 64 GB of RAM and require a kubelet reservation of approximately 6 GB of memory.

However, a new infra node will not be able to join the cluster because it initially joins as a worker node, and the worker kubelet reservation [119 GB] exceeds the physical memory [64 GB] available on the infra node.

4. List any affected packages or components.

No infrastructure nodes can be provisioned. This makes all maintenance work impossible and prevents responses to infrastructure events.