oc Get ClusterOperators¶
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.
When You Need This Command¶
Use this command when you need to inspect, change, or verify OpenShift resources from the terminal without relying on the web console.
Syntax¶
oc <command> <resource> [name] -n <project>
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.
Production Notes¶
Run read-only commands first, check the active project, and prefer declarative manifests for repeatable changes.
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¶
oc Get ClusterOperators is most useful when paired with verification. Check the project, run the command against the intended object, and confirm the resulting OpenShift state.