OpenShift MachineConfig Explained¶
Introduction¶
MachineConfigPools apply node-level configuration. Updating or Degraded states often mean a node failed to drain, reboot, or apply rendered configuration.
Core Concepts¶
OpenShift builds on Kubernetes with projects, Routes, ImageStreams, Builds, Operators, SCCs, and integrated platform administration.
Practical Examples¶
oc get machineconfigpool
oc describe mcp worker
oc get nodes -l node-role.kubernetes.io/worker
oc adm drain worker-1 --ignore-daemonsets --delete-emptydir-data
Example output:
NAME CONFIG UPDATED UPDATING DEGRADED MACHINECOUNT READY UPDATEDMACHINECOUNT DEGRADEDMACHINECOUNT
worker rendered-worker-9c7d8f5b2a1c4e6f8d0a True False False 3 3 3 0
Verification¶
oc get mcp worker
oc describe mcp worker
oc get nodes
Common Mistakes¶
- Forcing node changes while the MCP is already degraded.
- Ignoring PodDisruptionBudgets during drains.
- Editing rendered MachineConfig objects directly.
Quick Checklist¶
- Confirm the active project.
- Inspect the exact object named in the error.
- Read recent events.
- Apply one focused fix.
- Verify status after the change.
Related Guides¶
Summary¶
OpenShift MachineConfig Explained is best understood through the OpenShift objects involved and the oc commands that verify their current state.