

Lumovi served from a cluster, with the menu of who's signed in open.
Before you start
- A cluster running Kubernetes 1.28 or later, for signing in with a token.
- Helm and kubectl on your computer, with access to install into a namespace, and to bind a cluster role for the token below. Single sign-on and a proxy need more: see Install.
Try it
1
Install the chart
2
Live usage, if your cluster has none
The overview’s CPU and memory, and the usage on lists, come from metrics-server. Many clusters have it: if On kind, each kubelet’s certificate is its own, not signed by the cluster’s authority, so metrics-server can’t check it and reads nothing. There, tell it not to check, which is fine for a cluster you’re trying things on:Usage shows a minute or so later.
kubectl top nodes answers, yours does, and you can skip this. Everything else works without it. To add it:3
Open it
Forward a port to it, and open http://localhost:8080.If something else has port 8080, choose another, like
8081:80, and open that port instead.4
Get a token to sign in with
Lumovi asks for a bearer token the cluster accepts, and sends your requests with it. For a quick look, make a service account that can view everything, and a token for it that’s valid for an hour. Kubernetes’ own
view role leaves out nodes, which the overview reads, so it gets those too:5
Sign in
Paste the token and choose Sign in. You’re on the cluster’s overview, with exactly the access those two roles give.



Lumovi never gives anyone more than their own permissions. Bind a role like
edit instead of view, and the same page offers scaling, restarts and the rest.Make it your team’s
Give it an address
Turn on the chart’s ingress, with TLS, so people open it at a URL of its own.
Single sign-on
Sign in with Okta, Entra ID, Google, Keycloak, Dex or any OpenID Connect provider.
Behind a proxy
Let oauth2-proxy or Pomerium sign people in, and pass on who they are.
Keep it safe
What to know about impersonation, sessions and read-only mode.
How it differs from the desktop app
It’s the same app, so nearly everything in these docs applies to both. Served from a cluster:- It shows one cluster, the one it runs in, unless you set it up as a fleet. With one cluster, there’s no list of clusters to switch between.
- There’s no port forwarding, since there’s no computer of yours to forward a port to.
- There are no terminals, since they run a shell on your own computer.
- Charts come from repositories, registries or URLs, never from files on your computer.
- Clusters’ settings belong to the server, the same for everyone: whether a cluster is read-only, where its usage history comes from, and where its node shells run. Lumovi’s admins change them, or anyone, where there are none. Each browser keeps its theme.
- A few shortcuts belong to the browser: ⌘N and ⌘1…6 (Ctrl on Windows and Linux). The command palette (⌘K) has those commands.