Skip to main content
Lumovi works from the keyboard as well as the mouse. Press ? anywhere to see the shortcut sheet. It’s also in the command palette, and in the desktop app’s Help menu.
The Lumovi keyboard shortcuts sheet, grouped into General, Lists, Open object, Terminal and Go to.The Lumovi keyboard shortcuts sheet, grouped into General, Lists, Open object, Terminal and Go to.

The shortcut sheet, one keystroke away.

Shortcuts are written for macOS. On Windows and Linux, use Ctrl wherever you see ⌘, and Alt wherever you see ⌥. On a Mac, most shortcuts also work with Ctrl, but the ones that are only in the menus (⌘⇧C, ⌘/) and the editors’ (⌘S, ⌘F, ⌘Z) need ⌘. The terminals’ keys differ more, so they’re written out for both.
These are Lumovi’s own keys. Where you’ve changed one, the menus, the command palette, the shortcut sheet and tooltips show yours.

Change a shortcut

In Settings, Keyboard shortcuts lists every command, grouped as the shortcut sheet is; search it by a command’s name or its keys. Choose a command, and press its new keys. Esc cancels, and so does a click elsewhere, or the window losing the focus. A command you changed says Changed, with ↺ to put its own keys back. Reset all… puts back every command’s, and is off while none is changed.
  • Keys another command has where both work are asked about first, like ”⌘[ is Back’s. Use it here, and Back has no keys until you give it some.” Keys a command has only in one place, like a list or a terminal, are asked about too: give them to a command that works everywhere, and in that place they stay the other command’s while it has the keyboard.
  • Refused, saying why: the system’s own keys, like ⌘C, ⌘Q or ⌘W, and on Windows and Linux the ⊞ keys; for a terminal’s own commands, keys its program takes, a key with no ⌘ or ⌥ or ⌃, and ⌃ and a letter; keys a command your organization set has; and the keys marked Built in, which can’t be changed: moving through a list, Esc, the go-to keys, ⌥1–9 and ⌥⇧1–9, ⌘1–6, zoom, F2 and ⌘↵.
  • Putting back a command’s own keys, where another command has taken one since, asks first.
Your keys are kept with your settings: in the desktop app on this computer, and on a server for you, on every device you sign in from. A phone has no keys to change. Your organization can set a command’s keys, and lock that command: in the desktop app’s policy file, or on a server with LUMOVI_SETTINGS.

General

Desktop app only

These are in the app’s menus, and work in the desktop app. On a Mac, the menus are in the menu bar. On Windows and Linux, whose window has none, they’re behind the Menu button at the window’s top left, which Alt on its own, or F10, opens too, but not while a terminal has the focus: those keys are its program’s then. A browser keeps ⌘N and ⌘1…6 for its own windows and tabs, so when Lumovi runs in your cluster, use the command palette for those instead. In a terminal on a Mac, ⌘N opens another terminal instead of Create…, and ⌘W and ⌘K close and clear the terminal instead of closing the window and opening the command palette. See Terminals.

Go to a page

Press G, then a letter, within a second or so. Hover an item in the sidebar to see its letter. ReplicaSets, Autoscalers, Network Policies, Volumes, Storage Classes, API resources, Right-sizing, plugin pages and custom resources have no letter. Open them from the sidebar, or type their name into ⌘K.
Single-key shortcuts like G, / and ? don’t fire while you type in a field or a terminal, or while a dialog or menu is open, so they never get in your way.

Lists

While the detail panel is open, moving through the list opens each row in turn. In the filter box, ↓ moves into the list and Esc leaves the box. See Several at once for what to do with a selection.

The open object

With a menu or a dialog open, Esc closes that first, and the panel stays open. The panel’s edge can be dragged to resize it, or focused and moved with ← →. Lumovi remembers its width. See Object details.

Dialogs

Dialogs that delete, drain or uninstall open with the focus on Cancel, or on the field where you type the name, so a stray ↵ never confirms them. See Changing things safely.

An assistant’s change

When an AI assistant asks to change something, in the desktop app or on a server, its approval dialog takes: The dialog opens with nothing focused, so a stray ↵ doesn’t answer it. Its buttons show the keys: ⌘↩ on a Mac, Ctrl+↩ on Windows and Linux. In the desktop app, the shortcut sheet lists ⌘↵ under General, as Approve an AI assistant’s change. See Approving changes.

Editing YAML

Esc doesn’t close the panel while you’re editing, so a stray keystroke never loses your work. See Edit YAML, and Checked as you type for the schema’s keys. The editor in Create and those in Helm’s upgrade and install dialogs work the same way: there, ⌘S creates the objects, or reviews the values.

The map

In an object’s Map tab: On the Map page, in Find on the map:

Charts

On the Metrics page and in every Metrics tab:

Logs

Everything else in the log viewer is a button or a chip. See Logs.

The audit log

On the Audit log page:

Terminals

In the desktop app’s terminals, at the bottom of a cluster’s pages. Their keys differ by platform:
  • ⌃` and ⌃⇧` work anywhere in a cluster, in a terminal too. The start screen has no dock.
  • On a Mac, ⌘T, ⌘N, ⌘W and ⌘K are the terminal’s while a terminal has focus, as in Terminal and iTerm. Everywhere else they keep their usual meaning.
  • On Windows and Linux, a shell keeps CtrlW, CtrlK and the rest for itself, so the dock’s keys add ⇧, as Windows Terminal’s do. They, and the keys that switch terminals, work while the dock is open and has focus.
Other keys go to the terminal’s shell, as in any terminal, Ctrl keys included. On Windows and Linux, CtrlK and CtrlR are the shell’s there: click the page, or hide the dock, to use Lumovi’s. On a Mac, the menus’ ⌘ shortcuts, like ⌘R, still work.

Start screen and command palette

The command palette finds views, objects, namespaces and clusters, and the actions for the open object. See Search, filters and ⌘K.

A fleet’s page of clusters

When Lumovi shows a fleet, its first page has every cluster you may see, as cards. In Find a workload, ↑ ↓ move through the workloads it found, ↵ opens one in its cluster, and Esc closes it.