MachineConfigPool name and kubelet/containerruntimeconfigs role must be the same

Author: Michael Burke

modules/create-a-containerruntimeconfig-crd.adoc

@@ -92,7 +92,7 @@ spec:
    overlaySize: 8G <3>
    defaultRuntime: "crun" <4>
 ----
-<1> Specifies the machine config pool label.
+<1> Specifies the machine config pool label. For a container runtime config, the role must match the name of the associated machine config pool.
 <2> Optional: Specifies the level of verbosity for log messages.
 <3> Optional: Specifies the maximum size of a container image.
 <4> Optional: Specifies the container runtime to deploy to new containers. The default value is `runc`.

modules/create-a-kubeletconfig-crd-to-edit-kubelet-parameters.adoc

@@ -16,12 +16,32 @@ As the fields in the `kubeletConfig` object are passed directly to the kubelet f
 
 Consider the following guidance:
 
-* Create one `KubeletConfig` CR for each machine config pool with all the config changes you want for that pool. If you are applying the same content to all of the pools, you need only one `KubeletConfig` CR for all of the pools.
-
 * Edit an existing `KubeletConfig` CR to modify existing settings or add new settings, instead of creating a CR for each change. It is recommended that you create a CR only to modify a different machine config pool, or for changes that are intended to be temporary, so that you can revert the changes.
 
+* Create one `KubeletConfig` CR for each machine config pool with all the config changes you want for that pool.
+
 * As needed, create multiple `KubeletConfig` CRs with a limit of 10 per cluster. For the first `KubeletConfig` CR, the Machine Config Operator (MCO) creates a machine config appended with `kubelet`. With each subsequent CR, the controller creates another `kubelet` machine config with a numeric suffix. For example, if you have a `kubelet` machine config with a `-2` suffix, the next `kubelet` machine config is appended with `-3`.
 
+[NOTE]
+====
+If you are applying a kubelet or container runtime config to a custom machine config pool, the custom role in the `machineConfigSelector` must match the name of the custom machine config pool. 
+
+For example, because the following custom machine config pool is named `infra`, the custom role must also be `infra`:
+
+[source,yaml]
+----
+apiVersion: machineconfiguration.openshift.io/v1
+kind: MachineConfigPool
+metadata:
+  name: infra
+spec:
+  machineConfigSelector:
+    matchExpressions:
+      - {key: machineconfiguration.openshift.io/role, operator: In, values: [worker,infra]}
+# ...
+----
+====
+
 If you want to delete the machine configs, delete them in reverse order to avoid exceeding the limit. For example, you delete the `kubelet-3` machine config before deleting the `kubelet-2` machine config.
 
 [NOTE]