Skip to main content
Kubernetes records an event when something happens to an object: a pod is scheduled, an image fails to pull, a probe fails, a node runs low on memory. Events lists them, newest first. Open it from the sidebar under Cluster, with G then E, or with ⌘6 in the desktop app (Ctrl6 on Windows and Linux).
The Events list: warnings like BackOff, Failed and FailedScheduling among normal events, each with its object, message, count and when it was last seen.The Events list: warnings like BackOff, Failed and FailedScheduling among normal events, each with its object, message, count and when it was last seen.

What happened in the cluster, newest first.

​
Only the warnings

The chips above the list count each type. Pick Warning to hide the routine events. The overview’s Warnings tile opens the list this way. The filter (/) matches an event’s reason, message and object name as well as its labels, so typing OOMKilled or a pod’s name finds what you’re after.

​
An object’s own events

Every object’s detail panel has an Events tab with the events about it, newest first. It’s often the fastest way to see why a pod won’t start or a volume won’t bind. The overview lists the latest warnings across the namespace, too.
Kubernetes keeps events for a limited time (an hour, unless the cluster is set up otherwise), so old ones disappear. For a longer view of what a workload did, see Usage history and its logs.

Overview

The latest warnings, next to what needs attention.

Health and status

What the statuses on each object mean.