Kubernetes event
A short, time-stamped record a component writes into the cluster to say what it did or why it could not, such as Scheduled or FailedMount.
In more detail
Events name the component that reported them, the object involved, a reason and a message, so they show which part of the cluster made a decision. They are the first evidence to collect in almost every troubleshooting lesson, and kubectl describe prints them at the end. Events expire after about an hour by default, so capture them before you change anything.
Examples
kubectl get events --sort-by=.lastTimestamp | tail -n 4kubectl get events --field-selector reason=ScheduledRelated terms
- kubectl describe — The kubectl command that prints a readable summary of an object: its settings, current status and recent events.
- field selector — A kubectl filter that selects objects by the value of a field, such as an event's reason, rather than by label.
- spec and status — The two halves of most Kubernetes objects: spec is what you ask for, and status is what the cluster reports is actually true.
Taught in
- Monitoring With The Built-in CLI — Certified Kubernetes Application Developer (CKAD) Exam Prep
- Observability: Timed Drill And Checkpoint — Certified Kubernetes Application Developer (CKAD) Exam Prep
- Control Plane: etcd, API Server, Scheduler, Controllers — Kubernetes: Production-Grade Container Orchestration
- Troubleshooting: Pending Pod Triage — Kubernetes: Production-Grade Container Orchestration
- Troubleshooting: GitOps Drift And Controller Failures — Kubernetes: Production-Grade Container Orchestration