1. Proposed title of this feature request

Support using a single KubeletConfig across multiple MCPs.

2. What is the nature and description of the request?

This RFE originated from the discussion in the bug https://issues.redhat.com/browse/OCPBUGS-65772. According to the Red Hat documentation (https://docs.redhat.com/en/documentation/openshift_container_platform/4.20/html/machine_configuration/machine-configs-custom#create-a-kubeletconfig-crd-to-edit-kubelet-parameters_machine-configs-custom), it states: “Create one KubeletConfig CR for each machine config pool with all the config changes you want for that pool.”

In scenarios where the same configuration needs to be applied to multiple MCPs, creating separate KubeletConfig resources for each machine config pool becomes unnecessary overhead, especially since it already works correctly when based on MCP labels for existing MCPs. The issue mainly arises during reconciliation when a new MCP is created with the same label, which then requires a manual restart of the machine-config and machine-controller pods.

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

If the Kubelet configuration is the same, creating multiple KubeletConfig resources for each MCP with identical content is unnecessary overhead.

4. List any affected packages or components.

kubeletconfig