Skip to content

TELCODOCS-2703 DITA migration cleanup for troubleshooting-mco.adoc #111648

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
lcavalle wants to merge 1 commit into
base: main
Choose a base branch
from
Open

TELCODOCS-2703 DITA migration cleanup for troubleshooting-mco.adoc #111648

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions modules/troubleshooting-mco-apply-several-mcs.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand All @@ -27,5 +28,5 @@ $ oc patch mcp/<mcp_name> --type merge --patch '{"spec":{"paused":true}}'
----
$ oc patch mcp/<mcp_name> --type merge --patch '{"spec":{"paused":false}}'
----

This allows the nodes in your MCP to reboot into the new configurations.
+
This allows the nodes in your MCP to reboot into the new configurations.
1 change: 1 addition & 0 deletions modules/troubleshooting-mco-purpose.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down