OpenShift Console Explained¶
Introduction¶
Control plane troubleshooting should stay evidence-driven. Check ClusterOperators, component pods, recent events, and logs before restarting anything.
Core Concepts¶
OpenShift builds on Kubernetes with projects, Routes, ImageStreams, Builds, Operators, SCCs, and integrated platform administration.
Practical Examples¶
oc get clusteroperators
oc get pods -n openshift-etcd
oc logs -n openshift-etcd -l k8s-app=etcd --tail=50
oc get events -n openshift-etcd --sort-by=.lastTimestamp
Example output:
NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE
etcd 4.15.12 True False False 8d Etcd is available.
Verification¶
oc get co etcd kube-apiserver console
oc get pods -n openshift-etcd
oc get events -n openshift-etcd
Common Mistakes¶
- Restarting control plane pods without reading the operator message.
- Ignoring certificate or quorum warnings.
- Troubleshooting from a stale kubeconfig context.
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 Console Explained is best understood through the OpenShift objects involved and the oc commands that verify their current state.