Using Glauco
Cluster health
See crashing pods, failed pulls, unready nodes and other problems on one screen.
Open Cluster health
Click Cluster health in the sidebar, or press ⌘5 on macOS, or Ctrl5 on Windows and Linux. The title shows the number of issues.
Glauco checks pods, Deployments, StatefulSets, DaemonSets and Jobs in the namespace you picked, and every node. It ranks what it finds in one list.
What it finds
- CrashLoopBackOff
- A container keeps crashing and restarting.
- OOMKilled
- A container used more memory than its limit.
- ImagePullBackOff, ErrImagePull
- Kubernetes cannot pull the image.
- Unschedulable
- No node can take the pod.
- NotReady
- A node or pod is not ready.
- Frequent restarts
- 5 or more restarts, with one in the last hour.
- SchedulingDisabled
- A node is cordoned.
Workloads and jobs that are not at their desired state show their status. Click a row to open the object. With nothing to report, the screen says No problems detected.
On the Dashboard
The Dashboard shows the same problems in Needs attention, next to Cluster CPU, Cluster memory, Top CPU consumers, Top memory consumers and Recent events.
Still stuck? Contact us.