OpenShift ClusterOperators Explained¶
Introduction¶
ClusterOperators report health for core OpenShift components. A Degraded or Progressing operator should be investigated with its status message, related pods, and namespace events.
Core Concepts¶
OpenShift builds on Kubernetes with projects, Routes, ImageStreams, Builds, Operators, SCCs, and integrated platform administration.
Practical Examples¶
oc get clusteroperators
oc describe clusteroperator ingress
oc get pods -n openshift-ingress-operator
oc get events -n openshift-ingress-operator --sort-by=.lastTimestamp
Example output:
NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE
ingress 4.15.12 True False False 8d The ingress operator is available.
Verification¶
oc get co ingress
oc describe co ingress
oc get pods -n openshift-ingress-operator
Common Mistakes¶
- Reacting only to the table status and ignoring the message.
- Checking application namespaces for platform operator pods.
- Restarting operator pods before reading events.
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 ClusterOperators Explained is best understood through the OpenShift objects involved and the oc commands that verify their current state.