kubectl does, and keeps your credentials on your computer. You don’t need kubectl installed.
Download Lumovi
The website picks the right installer for your computer. Every installer is also on the latest GitHub release.
Install
- macOS
- Windows
- Linux
For macOS 13 (Ventura) or later, on Apple silicon and Intel. The app is signed and notarized by Apple.With Homebrew, name the cask in full:It installs the same disk image, from Lumovi’s tap. Lumovi keeps itself up to date as before, so
brew upgrade leaves it alone. brew uninstall --cask --zap lumovi also removes its settings, its own audit log, caches and logs.Or download it yourself:1
Download the disk image
Pick the one for your Mac:
Not sure which you have? Choose Apple menu → About This Mac, and look at Chip or Processor.
2
Drag Lumovi to Applications
Open the
.dmg, and drag Lumovi into the Applications folder.3
Open it
Open Lumovi from Applications, Launchpad or Spotlight. It finds your clusters straight away.
Prefer a
.zip? Each release has one for Apple silicon and one for Intel, next to the disk images.Open your first cluster
Lumovi starts on a list of every cluster in your kubeconfig, each with a status: its Kubernetes version and how fast it answered, or why it can’t be reached. A cluster that signs in through a program, likeaws, gke-gcloud-auth-plugin or kubelogin, says Signs in when opened instead, and signs in when you open it.


The start screen: every context in your kubeconfig, checked as it opens.
More than one window
File → New Window (⌘⇧N, Ctrl⇧N on Windows and Linux), or New window in the command palette, opens another window on the start screen, so two clusters can be open side by side. Each window has its own pages. What a window starts, a terminal, a pod’s logs, a copy or a port forward, is its own: it goes on whatever the other windows do, and ends when its window closes. The menu’s commands go to the window in front.Opened again as it was
The next time Lumovi starts, each window opens again where it was on the screen, on its page, with the panel’s object and what it had below:- A window that was on a cluster that signs in through a program opens the start screen instead, and that cluster is read when you open it. So does one whose cluster has gone from your kubeconfig.
- A terminal comes back ended: “The shell ended when Lumovi quit.”, with “A terminal’s shell can’t outlive Lumovi. Its name, cluster and namespace are kept for a new one.” Nothing runs until you choose Start a new shell: a shell runs your profile.
- An object kept below reads again as if just opened, on its overview if it was on its Shell, so no shell starts by itself. One on a cluster that signs in through a program waits, its tab saying not read yet, with a card: Not read yet, “production signs in through kubelogin, so Lumovi reads this when you ask.”, and Read it now. It’s read when you choose that, pick its tab, or open its cluster in that window.
- A tab moved into a window of its own opens again in its window, where it was: a terminal ended, an object as above. If only such windows were open, each opens as a Lumovi window on its tab’s cluster, with the tab below, unless that cluster signs in through a program: then on the start screen.
Take the tour
Five minutes through the app’s main ideas.
Connecting clusters
Multiple kubeconfigs, credential plugins, and what each status means.
Staying up to date
Lumovi keeps itself up to date. It looks for a new version shortly after it starts and every few hours after that, downloads it in the background, and installs it when you quit. When one is ready, a notice says so, with Restart now and What’s new. Close it, and the new version installs when you quit.- Help → Check for Updates… looks right away, and says what it found: Lumovi is up to date, Downloading Lumovi …, or Couldn’t check for updates, with the reason.
- Help → Check for Updates Automatically turns the background checks off.
.deb or .rpm install updates through your package manager, so installing a new version asks for an administrator password.
New versions come from the project’s GitHub releases, over HTTPS. Each download is checked against the checksum the release lists, and the new version must be signed as this one is: on macOS with the same Developer ID, and on Windows by Open Source Developer Péter Kóta. A copy that can’t update itself says so when you check: install new versions of it from the releases page.
Verify your download
Every release lists the SHA-256 checksum of each installer inSHA256SUMS.txt. Each installer has a signed build provenance attestation, which says it was built by Lumovi’s release workflow from the release’s commit, and an attested bill of materials: Lumovi-<version>.cdx.json (CycloneDX), every package the app bundles or ships, Electron, and the helm it ships with (4.3.0), with the Go modules that helm is built from and the Go it’s built with, on the release too. A scanner like grype reads it, and finds known vulnerabilities in any of them.
Releases are immutable: once one is published, GitHub keeps its files and its tag from being changed or replaced, and attests what it was published with, so gh release verify-asset checks that a download is the one the release has.
Requirements
macOS13 (Ventura) or later
Windows10 or later
LinuxRecent, 64-bit
Kubernetes1.25 or later
- Neither kubectl nor Helm is needed. Lumovi talks to the API server itself, and ships with the helm its Helm actions run. Each terminal gets a kubectl that matches its cluster.
- Kubernetes 1.27 or later lets Lumovi explain fields from the cluster’s own OpenAPI schema. Older clusters work, without the explanations.