diff --git a/modules/troubleshooting-mco-apply-several-mcs.adoc b/modules/troubleshooting-mco-apply-several-mcs.adoc index 94f75646066c..8f01ae583b13 100644 --- a/modules/troubleshooting-mco-apply-several-mcs.adoc +++ b/modules/troubleshooting-mco-apply-several-mcs.adoc @@ -6,6 +6,7 @@ [id="troubleshooting-mco-apply-several-mcs_{context}"] = Applying several machine config files at the same time +[role="_abstract"] When you need to change the machine config for a group of nodes in the cluster, also known as machine config pools (MCPs), sometimes the changes must be applied with several different machine config files. The nodes need to restart for the machine config file to be applied. After each machine config file is applied to the cluster, all nodes restart that are affected by the machine config file. @@ -27,5 +28,5 @@ $ oc patch mcp/ --type merge --patch '{"spec":{"paused":true}}' ---- $ oc patch mcp/ --type merge --patch '{"spec":{"paused":false}}' ---- - -This allows the nodes in your MCP to reboot into the new configurations. \ No newline at end of file ++ +This allows the nodes in your MCP to reboot into the new configurations. diff --git a/modules/troubleshooting-mco-purpose.adoc b/modules/troubleshooting-mco-purpose.adoc index 8a09975325b9..15f8bb3c22af 100644 --- a/modules/troubleshooting-mco-purpose.adoc +++ b/modules/troubleshooting-mco-purpose.adoc @@ -6,6 +6,7 @@ [id="troubleshooting-mco-purpose_{context}"] = Purpose of the Machine Config Operator +[role="_abstract"] The Machine Config Operator (MCO) manages and applies configuration and updates of {op-system-first} and container runtime, including everything between the kernel and kubelet. Managing {op-system} is important since most telecommunications companies run on bare-metal hardware and use some sort of hardware accelerator or kernel modification. Applying machine configuration to {op-system} manually can cause problems because the MCO monitors each node and what is applied to it.