Skip to main content
Two habits cover most of it: press ⌘K to go anywhere, and press / to filter the list you’re on. On Windows and Linux, use Ctrl instead of ⌘.

The command palette

Press ⌘K (or click Search… in the header) and type. Case doesn’t matter. Views and commands match when every word you type appears in them, in any order, so vol cl finds Volume Claims. Objects match when their name contains what you typed.
The command palette open over the app, with check typed, and the three checkout pods that match under Objects.The command palette open over the app, with check typed, and the three checkout pods that match under Objects.

Finding anything in the cluster, or anything to do, from the keyboard.

Results come in groups: Move with ↑ ↓, press ↵ to pick, and Esc to close. ⌘↵, from any row, opens Search for what you typed, as does Search the cluster for ”…”, the last row. With nothing typed, your saved searches are there too. New terminal opens a terminal in the dock at the bottom of the page: your own shell, with kubectl pointed at the cluster you’re in and its namespace. The palette shows its key, ⌃⇧`, which works anywhere in a cluster. Typing kubectl or shell finds it too. AI assistants… opens the AI assistants page: connect an assistant (turning them on, in the desktop app), see the ones you allowed on a server, say what they may do, and see what they did. Typing mcp finds it too. Audit log opens the audit log: what was done through Lumovi, by whom, and how it went. Typing history, who changed what or security finds it too. On a server, Your access says what Lumovi’s admins let you do, and why: see Your access. Typing permissions or why can't I finds it too. Admins also have Access, marked Admin, which opens the Access pages.
Some views answer to other words too: prometheus or usage history finds Metrics, recommendations or over-provisioned finds Right-sizing, charts finds Helm releases, and crds finds API resources.
The palette looks in the cluster you’re in. In a fleet, to find a workload in any of its clusters, use Find a workload on the page of every cluster: it looks for Deployments, StatefulSets, DaemonSets and CronJobs by name or namespace in all of them at once. There, ⌘K goes to the search box that finds clusters.

Go-to keys

Every main view has a two-key shortcut: press G, then a letter, within about a second. For example G P for Pods, G D for Deployments. The sidebar shows each view’s keys when you hover it, and Keyboard shortcuts lists them all.

The sidebar

From top to bottom, the sidebar has:
  • The cluster switcher: the cluster you’re in, its Kubernetes version, and a lock when it’s read-only. Open it to switch clusters, in the desktop app or a fleet. See Connect your clusters.
  • Overview, Workloads, Map, Pods, Metrics (with its Right-sizing tab), Helm releases and Search. Workloads stays highlighted on the list of each workload kind.
  • Cluster, Network, Configuration, Storage and Access control: Kubernetes’ own kinds, like Nodes, Services, Secrets, Volume Claims and Roles. Plugins that extend them sit with them when the cluster has them: Cilium, Gateway API, Linkerd and Traefik under Network, Sealed Secrets under Configuration, Longhorn, Rook Ceph and Volume Snapshots under Storage.
  • Pinned: the kinds you pinned, in every cluster that serves them, then the objects you pinned in this cluster, each with its status. Pin a custom kind from the pin button above its list, or from API resources.
  • Plugins: a page for each of the other tools the cluster runs, like Argo CD, cert-manager or Karpenter.
  • Custom resources: the custom kinds you opened last in this cluster (up to five), then API resources, with how many custom kinds the cluster serves. Kinds you pinned, and kinds that belong to a plugin, aren’t repeated here.
At the bottom are the theme, AI assistants (the sparkles, with a green dot while an assistant is connected; on a server, unless its administrator turned them off), Audit log (the scroll), Admin: who may do what (the shield, for Lumovi’s admins), your account when Lumovi runs in your cluster, a link to Lumovi on GitHub, and the version you’re running. ReplicaSets and Autoscalers have lists of their own, but no place in the sidebar: find them with ⌘K.

Narrowing a list

Lists of objects, the Workloads page and plugin pages all have the same three tools above them. Helm releases has the first two.

Health

The chips count each health level in the list: Failing, Warning, In progress, Healthy, Inactive (some kinds use their own words, like Running for pods). Click one to show only those, and click more to add them. Click it again to clear it.

Filter

Press /, or click the filter box, and type. It matches, without case:
  • names and namespaces
  • labels, written as key=value, like app=checkout
  • for events, the reason, message and object’s name
  • for custom resources, what the list’s columns show
On the Workloads page, the filter also matches each workload’s kind and images. On a plugin’s page, it matches each object’s kind and what its status says, like the reason it failed. ↓ moves from the filter into the list. Esc leaves the filter.

Label selector

The label selector is sent to the cluster, which does the filtering, so it’s the way to narrow lists in big clusters. It takes Kubernetes’ own syntax; press ↵ to apply it.
A list stops at 5,000 objects (or LUMOVI_MAX_LIST_ITEMS). When there are more, it says so, with Filter by label, because a selector lets the cluster send only the ones you want.

Sorting and pages

  • Sort by clicking a column’s header, and again to reverse it. Not every column sorts: the name, status and age do, and so do numbers like restarts, CPU, memory, count and last seen, and the columns custom resources get from the cluster or a view.
  • Lists start sorted by status, the most urgent first; kinds with no status by name, and events by when they were last seen. Helm releases starts sorted by name.
  • With every column that sorts hidden, a list keeps its own order.
  • Pages hold 100 rows, or 50, 250 or 500 (Rows per page). Use ← → for the previous and next page. Helm releases shows every release on one page.

Columns

Columns, at the end of a list’s toolbar, chooses what the list shows. So does a heading’s right-click menu: Hide this column, or Columns… for the rest.
  • Show or hide a column with its box, and move it by dragging, or with ⌥↑ ⌥↓. A list’s name column stays first.
  • Add a column from a label or an annotation the listed objects carry: start typing its key, and the keys they carry are offered, the most common first. kubectl’s own annotations aren’t offered. An object without it shows a dash, and Remove this column takes it away again. Its values are the cluster’s text: a character that can’t be seen, or would turn the text round, shows as a mark, like U+202E.
  • Size a column by dragging its heading’s edge, or, with the heading focused, by 16 pixels with ⌥← ⌥→. Double-click the edge, or press ⌥0, to give it its own width again. A column is never narrower than 64 pixels or its heading’s first word, and the name never narrower than 160 pixels.
  • A list never scrolls sideways, at any width, beside the panel or not. Where there’s no room, the least important columns give way first; then the status narrows to its icon, in its colour, with its word in a tooltip; then the other columns give way, from the right; and last the name narrows, down to 140 pixels, cut in its middle so similar names stay told apart. In Events, the message stays, the type narrows to its icon, and the reason gives way. Where you chose or moved columns, they give way in your order instead, the last first, the status narrowing at its turn. Columns says how many aren’t drawn, and the menu marks each “doesn’t fit”.
  • Headings stay at the top as the list scrolls, and the rows don’t show through them.
On Windows and Linux, ⌥ is Alt. What you choose is kept for that kind in that cluster: in the desktop app, and on a server in the browser you chose it in. Reset brings back Lumovi’s own columns.

Copy and download

  • Copy, the first button in the bar of picked rows, or ⌘C in the list, copies the picked rows as the list shows them: a heading row, then a row each, with a tab between columns. Each value is whole, with its line breaks and tabs as spaces.
  • Download CSV, in the Columns menu, saves every row the filters let through, not only the page you’re on, with the columns you show. Values are whole, times are in UTC (2026-10-13T09:12:03Z), and numbers have no units: CPU in cores and memory in bytes, as the headings say. The file is named for the kind, the namespace (or the cluster, with several picked) and the day, like pods-shop-2026-10-13.csv. It’s UTF-8 with lines that end in CRLF, as spreadsheets read it.
  • In both, a value that a spreadsheet would read as a formula (one starting with =, +, -, @, a tab or a carriage return) starts with ', so it’s shown as text and never run.
In the desktop app you choose where the file goes, and then Show in Finder (Show in Explorer on Windows, Show in folder on Linux) opens its folder. On a server, the browser downloads it.

Pin an object

To keep an object at hand, pin it: Pin on its page, or ⌥P; the pin at the end of its row in a list; or Pin in the command palette while it’s open. Up to 20 in a cluster. An Event can’t be pinned: it’s gone within the hour. Pinned objects stand in the sidebar under Pinned, after the kinds you pinned, each with its name and its status, in the order you pinned them. ⌥1 to ⌥9 open the first nine. (On Windows and Linux, ⌥ is Alt. A browser on Linux keeps Alt and a number for its own tabs: open them from the sidebar or the palette there.)
  • Move one by dragging it in the sidebar, or with ⌥↑ ⌥↓ in the palette’s Pinned group.
  • Unpin one with Pinned on its page, the pin in its row, or ⌫ in the palette’s Pinned group. Undo puts it back where it was.
  • One that’s gone says “Deployment cart in shop isn’t in the cluster any more.”, and one you can’t read any more says so. Either opens its kind’s list, filtered to its name, and has its own unpin button in the sidebar.
On a phone, the menu’s drawer holds the pins, and a long press opens a pin’s sheet, to open or unpin it.

Saved views

A list’s filter, health, labels, sort, columns and namespaces can be saved as a view, with a name, to come back to it. Views, in the list’s toolbar, saves what the list shows now (Save view…), and lists the kind’s saved views to open. The palette has them too: the views of the list you’re on, then the others. A view opened and then changed says so on the button, like Ready · changed, and Save changes to “Ready” keeps the change. Rename, move and delete views in the Views menu; a delete has Undo. Names are a kind’s own: two views of Deployments can’t have the same name. Up to 20 views of one kind, and 50 in a cluster. A view of a kind the cluster doesn’t serve any more says so.

Where pins and views are kept

  • In the desktop app, on your computer, for each cluster.
  • On a server, with who’s signed in, wherever Lumovi keeps its state: the chart’s Secret (auth.keepSessions), LUMOVI_DATA_DIR, or memory, where a restart loses them. So they’re the same in any browser you sign in from. Everyone who signs in with the same token shares one set.
A server keeps up to 32 kB of a person’s in one cluster, 96 kB of theirs in all, and 400 kB for everyone. A person’s are let go after 180 days without use. When everyone’s would pass 400 kB, those of clusters the server doesn’t show now go first, the longest unread first. Past a limit, a pin or a view isn’t saved, and Lumovi says which, like “This server keeps no more of your pins and views in this cluster. Unpin or delete some to save this.”

Moving through a list

Back and Forward

The filter, health chips, label selector, sort, page and the open object are all part of the page’s address. Back (⌘[ or Alt←) and Forward (⌘] or Alt→) bring each of them back, like in a browser. On Helm releases, only the open release is part of the address.
In your cluster: these addresses are real links. Copy one from the address bar to share a filtered list, or an open pod, with a teammate.
Copy link copies a link to what you’re looking at, for a teammate to open in their own Lumovi. It’s first in an open object’s More actions, and Copy link to this view is in the bar’s More (⋯). The command palette has whichever fits. In the desktop app, the link is a lumovi:// one, and Lumovi says “Link copied. It names the cluster, not how to reach it.” On a server, it’s the page’s own address. A lumovi:// link opens the same object or view in the desktop app of anyone who has that cluster in their kubeconfig, under whatever name. It carries:
  • Where to go: the page, the open object and its tab, and how the list is filtered and sorted.
  • Which cluster: its name in the kubeconfig it was copied from, and a short fingerprint of the cluster’s address and its certificate authority. Lumovi finds the cluster by the fingerprint, so a colleague’s other name for it doesn’t matter. The fingerprint doesn’t give the address away, but where a cluster has no authority of its own, someone who can guess its address can check a guess against it.
It never carries a credential, a user, a file, a command or a form, and it only shows. Every page and tab it can open only reads, and it never opens a shell, an attach or a port forward: a link to an object’s Shell opens it on its overview. A link to a plugin’s page carries the page alone. A link never opens anything by itself. It asks first, in a card at the top of the window in front, named for your own name for the cluster:
  • “Open checkout-7d9f in production?”, with Cancel, New window and Open, or “Go to … ?” with Go where a window already shows that cluster, which then asks there. Where the link calls the cluster something else, the card says “the link calls it …”. Where opening it signs in through a program, it says “Opening it signs in with aws.” Nothing connects, reads or signs in until you choose. Where the window has an edit that isn’t saved, New window comes first: “This window has an edit that isn’t saved, so it opens in a new one.”
  • Several of your clusters match: “Open … in which context?”, and you pick one.
  • Yours has the link’s name, but another address: “You have a cluster called production, but at another address than the link’s.”, with Open production anyway.
  • None of yours: “This link is to a cluster called production that isn’t in your kubeconfig. Ask whoever sent it which one it is, then add it.”, with Add a cluster.
  • A link that can’t be read isn’t opened: “This link can’t be opened: …”, with why. A part of it Lumovi doesn’t take is left out, and the card says what: “Some of the link was left out: the time range.”
Cancel has the keyboard, and for the first half second ↵, Space and Esc do nothing, so keys meant for something else don’t answer it; after that, Esc is Cancel. While you type in a terminal or a field, the card shows without taking the keyboard: ⌘L goes to it (Ctrl⇧L on Windows and Linux). A link that brings Lumovi forward from another app takes no keys until you stop typing. One link asks at a time, and a newer one takes its place. For two seconds after you answer one, links that come are let go, and Lumovi says once “Lumovi skipped a link that came right after the last one. Open it again if you meant to.” If a dialog is open, the link waits until you close it: “A link is waiting. Lumovi asks about it when this dialog closes.” A link that starts Lumovi asks once its windows are back where they were. Your organization can turn links off with the policy key links: Lumovi then opens none, and Copy link isn’t there.

Keyboard shortcuts

Every shortcut, in one place.

Several at once

Act on the rows you’ve picked.