oc Describe Pod Examples¶
Introduction¶
oc describe pod shows events, container states, image pulls, probes, mounts, and scheduling decisions for one pod. It is usually more useful than logs when the pod never started.
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 describe pod web-7c9d7f6f8b-jx4mk -n app
oc get events -n app --field-selector involvedObject.name=web-7c9d7f6f8b-jx4mk
oc logs web-7c9d7f6f8b-jx4mk -n app
Example output:
Events:
Type Reason Age From Message
Normal Scheduled 2m default-scheduler Successfully assigned app/web-7c9d7f6f8b-jx4mk to worker-1
Normal Pulled 2m kubelet Successfully pulled image
Verification¶
oc get events -n app --sort-by=.lastTimestamp
oc get pods -n app -o wide
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.
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 Describe Pod Examples is most useful when paired with verification. Check the project, run the command against the intended object, and confirm the resulting OpenShift state.