Skip to main content
This tour follows what you’d do on a day something breaks: see what’s wrong, find it, look closer, and fix it. Keyboard shortcuts are shown for macOS; on Windows and Linux, use Ctrl for ⌘.
1

See how the cluster is doing

Every cluster opens on its Overview. Four tiles say how many nodes are ready, how many pods are running, how many workloads are healthy, and how many warnings came in the last hour. Each tile links to its list, filtered to what’s wrong when something is.Below them, CPU and memory show what’s in use next to what’s requested, limited and allocatable, with a line of recent usage. Needs attention lists the pods and workloads in trouble, and Recent warnings the events that explain them.
A cluster's overview: nodes, pods and workloads, CPU and memory with their last hour, and what needs attention.A cluster's overview: nodes, pods and workloads, CPU and memory with their last hour, and what needs attention.
The namespace menu at the top scopes every list. It starts in your kubeconfig context’s namespace, and remembers your choice per cluster. More about the overview.
2

Find what's failing

Open Workloads (G then W). Every Deployment, StatefulSet, DaemonSet and CronJob is in one list, with the Jobs and pods that nothing else runs, each with its status, ready pods and the CPU and memory its pods use. Whatever is failing sorts to the top, whatever its kind.
Every workload, whatever its kind, in one list, with its health.Every workload, whatever its kind, in one list, with its health.
Statuses read the way you’d say them: Unavailable Degraded Running Ready. The chips above the list keep only what’s Failing, Warning, In progress, Healthy or Inactive. How health works.
3

Look closer

Click a row, or move to it with ↓ and press ↵. Its details open next to the list, so you keep your place: the facts that matter for its kind, its pods and why they restart, its events, logs and YAML.
A deployment that's failing, with its pods and why they're restarting.A deployment that's failing, with its pods and why they're restarting.
With the panel open, ↑ and ↓ open each row in turn, and Esc closes it. The detail panel.Its Map tab shows how it’s connected: what leads to it, like the gateway, ingress and services in front of it, and what it uses and runs on, down to the nodes. Whatever is missing or unwell along the way stands out.
The Map tab of a deployment: the gateway, HTTPRoute, ingress, services, network policies and autoscaler that lead to it above, and its pods, ConfigMap and service account below, with the pods on two nodes, one under memory pressure.The Map tab of a deployment: the gateway, HTTPRoute, ingress, services, network policies and autoscaler that lead to it above, and its pods, ConfigMap and service account below, with the pods on two nodes, one under memory pressure.
The map.
4

Read the logs

The Logs tab of a workload merges every one of its pods, in the order lines were written, each marked with its pod. Pods that start later join in. Keep only errors or warnings, leave a pod out, or search.
The logs of every pod of a deployment, merged as they happened.The logs of every pod of a deployment, merged as they happened.
A pod also has a Shell tab, for a terminal in its containers. Logs · Shells and debug containers.
5

Fix it, safely

The open object’s actions are right there: the common ones as buttons, the rest under ⋯ (or .). Every dialog names the cluster and shows the kubectl command it amounts to. Lumovi checks your permissions first, and disables what you can’t do, saying why.
Scaling a deployment, with what will change.Scaling a deployment, with what will change.
Once it’s done, the notification offers Undo for changes that can be taken back, like a scale. Changing things safely.
6

Go anywhere from the keyboard

Press ⌘K. Type a few letters to jump to any view, the page of a tool your cluster runs, any object already loaded, a namespace or another cluster, or to run an action on the object you have open.
Finding anything in the cluster, or anything to do, from the keyboard.Finding anything in the cluster, or anything to do, from the keyboard.
Most views also have a G shortcut, shown when you hover them in the sidebar, and ? lists them all. Keyboard shortcuts.

​
Where to next

Usage over time

Chart what namespaces, workloads and nodes use, from your Prometheus.

Right-sizing

What each workload should request, from a week of its usage.

The map

How an object is connected, from the gateway down to the nodes.

Helm releases

Every release, its values and revisions, and upgrades reviewed first.

Add-ons

A page for each tool your cluster runs, like Argo CD, cert-manager or Karpenter.

Read-only mode

Look around a production cluster with changes turned off.