Machine config pool degraded
A MachineConfigPool cannot roll its configuration to its nodes.
ImpactUpgrades stall, nodes stay cordoned
Can it be seen coming?No
RupturaNot covered yet
How to detect it
Degraded True.
Metrics and signals to watch:
MachineConfigPool conditions
Can you see it coming?
No This failure arrives without a reliable warning sign, so the goal is to detect it fast and explain it.
What it hits next
nodes of the pool.
What to do
Check the machine config daemon on the stuck node.
Sources
- OpenShift MachineConfigPool
Where Ruptura stands
Ruptura does not cover this failure yet. The card is here so you know it exists and how to detect it.
Related failures
- TLS certificate expires
- OpenShift cluster operator degraded
- OLM operator install fails
- Metrics target down
See it coming instead of reading about it
Ruptura is an open-source operator for Kubernetes and OpenShift that predicts the failures in this catalog that can be predicted, detects the others, and sends them to Alertmanager. Watch an OOM crash predicted 21 minutes early · ★ GitHub
Ruptura is an open-source operator for Kubernetes and OpenShift that predicts the failures in this catalog that can be predicted, detects the others, and sends them to Alertmanager. Watch an OOM crash predicted 21 minutes early · ★ GitHub