Merge pull request #87581 from openshift-cherrypick-robot/cherry-pick-87519-to-enterprise-4.16

[enterprise-4.16] OSDOCS#12977: Reference the config map in node pools

Author: xenolinux

hosted_control_planes/hcp-machine-config.adoc

@@ -8,10 +8,17 @@ toc::[]
 
 In a standalone {product-title} cluster, a machine config pool manages a set of nodes. You can handle a machine configuration by using the `MachineConfigPool` custom resource (CR).
 
+[TIP]
+====
+You can reference any `machineconfiguration.openshift.io` resources in the `nodepool.spec.config` field of the `NodePool` CR.
+====
+
 In {hcp}, the `MachineConfigPool` CR does not exist. A node pool contains a set of compute nodes. You can handle a machine configuration by using node pools.
 
 include::modules/configuring-node-pools-for-hcp.adoc[leveloffset=+1]
 
+include::modules/hcp-kubeconf-nodepool.adoc[leveloffset=+1]
+
 include::modules/node-tuning-hosted-cluster.adoc[leveloffset=+1]
 
 include::modules/sriov-operator-hosted-control-planes.adoc[leveloffset=+1]

modules/configuring-node-pools-for-hcp.adoc

@@ -22,7 +22,7 @@ On {hcp}, you can configure node pools by creating a `MachineConfig` object insi
 apiVersion: v1
 kind: ConfigMap
 metadata:
-  name: <configmap-name>
+  name: <configmap_name>
   namespace: clusters
 data:
   config: |
@@ -31,7 +31,7 @@ data:
     metadata:
       labels:
         machineconfiguration.openshift.io/role: worker
-      name: <machineconfig-name>
+      name: <machineconfig_name>
     spec:
       config:
         ignition:
@@ -65,9 +65,10 @@ metadata:
 # ...
 spec:
   config:
-  - name: ${configmap-name}
+  - name: <configmap_name> <1>
 # ...
 ----
+<1> Replace `<configmap_name>` with the name of your config map.
 
 //.Verification
 

modules/hcp-kubeconf-nodepool.adoc

@@ -0,0 +1,62 @@
+// Module included in the following assemblies:
+//
+// * hosted_control_planes/hcp-machine-config.adoc
+
+:_mod-docs-content-type: PROCEDURE
+[id="hcp-kubeconf-nodepool_{context}"]
+= Referencing the kubelet configuration in node pools
+
+To reference your kubelet configuration in node pools, you add the kubelet configuration in a config map and then apply the config map in the `NodePool` resource.
+
+.Procedure
+
+. Add the kubelet configuration inside of a config map in the management cluster by entering the following information:
++
+.Example `ConfigMap` object with the kubelet configuration
+[source,yaml]
+----
+apiVersion: v1
+kind: ConfigMap
+metadata:
+  name: <configmap_name> <1>
+  namespace: clusters
+data:
+  config: |
+    apiVersion: machineconfiguration.openshift.io/v1
+    kind: KubeletConfig
+    metadata:
+      name: <kubeletconfig_name> <2>
+    spec:
+      kubeletConfig:
+        registerWithTaints:
+        - key: "example.sh/unregistered"
+          value: "true"
+          effect: "NoExecute"
+----
+<1> Replace `<configmap_name>` with the name of your config map.
+<2> Replace `<kubeletconfig_name>` with the name of the `KubeletConfig` resource.
+
+. Apply the config map to the node pool by entering the following command:
++
+[source,yaml]
+----
+$ oc edit nodepool <nodepool_name> --namespace clusters <1>
+----
+<1> Replace `<nodepool_name>` with the name of your node pool.
++
+.Example `NodePool` resource configuration
+[source,yaml]
+----
+apiVersion: hypershift.openshift.io/v1alpha1
+kind: NodePool
+metadata:
+# ...
+  name: nodepool-1
+  namespace: clusters
+# ...
+spec:
+  config:
+  - name: <configmap_name> <1>
+# ...
+----
+<1> Replace `<configmap_name>` with the name of your config map.