🔔 Events
Events are Kubernetes' own notices: "the pod was scheduled", "the image was pulled", "the container failed". When a pod does not start, events usually explain why, even before any log exists.
Events are queried with kubectl. The Nuvion Panel does not have an events screen.
🚀 Before you start
- Have cluster access configured (see Cluster Access).
🚀 1. See the cluster events
kubectl get events -A --sort-by=.lastTimestamp
The most recent ones appear last.
🚀 2. See only the warnings
kubectl get events -A --field-selector type=Warning
Warning events indicate problems. Normal events are informational.
🚀 3. Trigger an error to see the event
Create a pod with an image that does not exist:
kubectl run erro-imagem --image=nginx:versao-que-nao-existe
kubectl get pods
The STATUS changes to ErrImagePull and then ImagePullBackOff.
🚀 4. See the pod events
kubectl describe pod erro-imagem
Scroll down to the Events section at the end. It shows, in order, what Kubernetes
tried to do and the error message, with the reason Failed and the text indicating that the
image was not found.
🚀 5. Follow events in real time
kubectl get events --watch
Exit with Ctrl+C.
📖 Most common events
| Reason | What it means |
|---|---|
Scheduled | The pod was assigned to a node |
Pulling / Pulled | The image is being pulled / was pulled |
Created / Started | The container was created / started |
Failed | Failure (see the message, such as image not found) |
BackOff | Kubernetes is waiting before trying again |
FailedScheduling | No node has resources for the pod |
Unhealthy | The health check (probe) failed |
Killing | The container is being terminated |
FailedMount | A disk or Secret could not be mounted |
✅ How to know it worked
The Events section from step 4 shows the image error.
Events are only available for a short time (about 1 hour). Check soon after the problem occurs.
❗ Common problems
| Symptom | Cause | Solution |
|---|---|---|
No resources found | Events have already expired or the namespace is wrong | Use -A and reproduce the problem |
| Old event causes confusion | The list is not sorted | Use --sort-by=.lastTimestamp |
🧹 Cleanup
kubectl delete pod erro-imagem
➡️ Next step: Alerts
🧠 Questions?
Talk to our SaveinCloud technical support team!