oc Get Events Examples¶
Introduction¶
OpenShift events explain recent scheduling, image pull, probe, mount, and admission failures. Sort them by timestamp so the latest failure appears at the bottom.
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 events -n app --sort-by=.lastTimestamp
oc get events -n app --field-selector type=Warning
oc describe pod web-7c9d7f6f8b-jx4mk -n app
Example output:
LAST SEEN TYPE REASON OBJECT MESSAGE
45s Warning Unhealthy pod/web-7c9d7f6f8b-jx4mk Readiness probe failed: HTTP probe failed with statuscode: 503
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 Get Events Examples is most useful when paired with verification. Check the project, run the command against the intended object, and confirm the resulting OpenShift state.