Skip to main content
Lumovi runs in a cluster as a dashboard for that cluster. It’s the same app as the desktop one, in a browser: people open its address, sign in, and see and change what their own Kubernetes permissions allow. Nobody installs anything, and a link to any page (a pod, its logs, a Helm release) can be shared.
Lumovi in a browser, showing a cluster's overview, with the account menu open: who is signed in, and their groups.Lumovi in a browser, showing a cluster's overview, with the account menu open: who is signed in, and their groups.

Lumovi served from a cluster, with the menu of who's signed in open.

Install it

One Helm chart, then a port-forward or an ingress. A few minutes.

Joining a team that runs it?

Nothing to install. Here’s how signing in works.

How it works

Lumovi runs as one pod with a Service in front of it. Each page in a browser keeps one WebSocket open to it, and Lumovi makes every request to the API server as the person who signed in, so the API server applies their RBAC. Lumovi never gives anyone more than their own permissions. It reaches the API server as that person in one of two ways:
  • With their own token. Their requests carry a token the cluster checks itself. Lumovi’s service account needs no permissions at all.
  • By impersonating them. Lumovi sends its service account’s credentials with Impersonate-User and Impersonate-Group headers. The API server checks that the service account may impersonate, then applies the person’s RBAC.
Which one depends on how people sign in.

Ways to sign in

When people’s own tokens reach the cluster, its audit log names them directly. When Lumovi impersonates them, the audit log records Lumovi’s service account acting as them. The chart grants the impersonation permission only in the modes that need it. A fleet signs people in with single sign-on or a proxy, never with tokens: a token says who someone is to one cluster only. It impersonates people in each cluster, with credentials for that cluster, or passes their own token on to the clusters that trust your provider.
Signing in with a token needs Kubernetes 1.28 or later: Lumovi asks the cluster whose token it is with a SelfSubjectReview. Single sign-on and the proxy work from Kubernetes 1.25, like the rest of Lumovi.

What’s different from the desktop app

It shows the cluster it runs in. To show many clusters, with a page that sums them all up and a list to switch between, run it as a fleet. A fleet’s Lumovi can run in a cluster, on a machine of its own or on a platform like Sevalla, and reaches clusters in private networks through agents that dial out to it.
There’s no computer of the user’s to forward a port to, so Forward a port… isn’t offered. See Port forwarding for the desktop app.
Terminals run a shell on your own computer, so Lumovi in a cluster has none: no dock, and no Paste in terminal by a dialog’s command. See Terminals for the desktop app.
Never from files on anyone’s computer. Lumovi fetches charts only from public addresses unless helm.allowPrivateCharts allows private ones, such as a ChartMuseum or Harbor in your network. Otherwise anyone signed in could make it reach services inside the cluster’s network. See Security.
Whether a cluster is read-only, where its usage history comes from, and where its node shells run are the server’s, the same for everyone on it and their AI assistants. Lumovi’s admins change them, or anyone, where there are none. readOnly: true makes every cluster read-only. Each browser keeps only its theme, and the namespace you picked. See Read-only mode.
AI assistants and agents, any MCP client, connect to Lumovi’s address over HTTP, at mcp, and sign in through it in the browser, with OAuth: people allow each one, and it acts as them. The changes they ask for wait on their own pages. Each person says what theirs may do, and where, within limits the administrator sets. See AI assistants on a server, and AI assistants for your team to turn them off or set limits.
Within what RBAC allows, its admins can let people do less through Lumovi, team by team: read-only for everyone, say, with shells and Secrets’ values only where a team works. Each person sees what they may in Your access. See Access for your team.
What everyone does through Lumovi, and who signed in, is kept on a volume, written to Lumovi’s output for your log collector, and sent to a webhook if you like. People see their own events, and the auditors you name see everyone’s. See Audit log for your team.
The server doesn’t update itself. See Upgrade.
Keyboard shortcuts are the same, except ⌘N and ⌘1…⌘6 (Ctrl on Windows and Linux), which browsers keep for themselves. The command palette (⌘K) has those commands. See Keyboard shortcuts.

Pages you can share

In a browser, every page has a real address: a list with its filters and sort order, an object’s detail panel, a Helm release. Copy the address bar and send it. Whoever opens it signs in, then lands on the same page, seeing what their own permissions allow.

The image

Imageghcr.io/lumovi/lumovi
Platformslinux/amd64, linux/arm64
Runs asNon-root, no shell
Writes to/tmp, and the audit log’s volume
The image has Node.js, helm and Lumovi, and nothing else. When people install, upgrade or roll back a Helm release through Lumovi, it runs that helm (Helm 4.3.0 in Lumovi 1.23.2), whatever helm they have on their own computers. Each release is attested with its build provenance, which the GitHub CLI checks, signed with cosign, and has a bill of materials:
The Helm chart is oci://ghcr.io/lumovi/charts/lumovi. It’s released with Lumovi itself, so the chart’s version is the app’s, and it’s attested and signed the same way: see Verify the image.

Requirements

  • Kubernetes 1.25 or later, and 1.28 or later to sign in with tokens.
  • Helm, to install the chart. Helm 3.8 and later read charts from OCI registries.
  • An ingress controller, if you want Lumovi at an address of its own. A kubectl port-forward is enough to try it.
  • A default storage class, or one you name, for the audit log’s volume. Or turn the volume off, and Lumovi keeps the log in memory.
  • On OpenShift, nothing more: the chart runs under its restricted-v2 security context constraint. See OpenShift.
  • Behind a company’s proxy, its address, and the certificate authority it signs with, if it inspects HTTPS. See Proxies and certificate authorities.
  • For a fleet, single sign-on or an authenticating proxy. Its Lumovi needs no Kubernetes of its own: it needs to reach each cluster’s API server, or each cluster’s agent needs to reach it.

Install it

Helm install, open it, sign in.

Security

What Lumovi can do, and how to keep it contained.