OpenShift Upgrade Checklist¶
Introduction¶
OpenShift administration tasks should be driven by cluster health, operator conditions, node status, and a rollback or backup plan. Inspect first, then change one cluster-scoped item at a time.
Why This Matters¶
OpenShift administration relies on operators and cluster-scoped resources. A bad change can affect many projects, so inspect status and events before applying fixes.
Practical Examples¶
oc get clusterversion
oc get clusteroperators
oc get machineconfigpool
oc adm must-gather
Example output:
NAME VERSION AVAILABLE PROGRESSING SINCE STATUS
version 4.15.12 True False 8d Cluster version is 4.15.12
Verification¶
oc get co
oc get mcp
oc get nodes
oc get events -A --sort-by=.lastTimestamp
Troubleshooting¶
Read the operator message, check the namespace where the component runs, inspect related events, and confirm whether the condition is Available, Progressing, or Degraded.
Common Mistakes¶
- Looking only at the final error and ignoring events.
- Checking the wrong project with oc.
- Changing several objects at once before confirming the current state.
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 Upgrade Checklist is an administration task that should be driven by cluster status, operator conditions, and component logs instead of broad restarts.