Skip to main content
When Lumovi runs in a cluster, it’s a web page. Open the address your team gave you, sign in, and the cluster’s overview opens. If your team’s Lumovi shows many clusters, a page of every cluster you may see opens instead: see In a fleet. Everything you see, and every change you can make, is what your own Kubernetes account allows: Lumovi never gives anyone more.

Sign in

How you sign in depends on how your team set Lumovi up. The sign-in page shows the right way.
Choose Sign in with … (your company’s provider, like Okta or Google), and sign in there as you usually do. You come back to Lumovi, signed in.
Lumovi served from a cluster: signing in with single sign-on.Lumovi served from a cluster: signing in with single sign-on.

In a fleet

Some teams run one Lumovi for many clusters. Once you’re signed in to one of those, its first page shows every cluster you may see, each on a card that sums it up: its nodes, pods and workloads, its warnings in the last hour, and its CPU and memory. The ones that need attention come first. Click a card to open its cluster. You sign in once, for all of them. In each cluster, you see and change what your account there allows, so one may let you do more than another. To move to another cluster, open the cluster’s name at the top of the sidebar, or type its name into the command palette. All clusters, in both, goes back to the page of every cluster. If one cluster doesn’t accept your sign-in, its card says Unauthorized. You stay signed in, and the other clusters work as before. See Clusters in a fleet for the page of every cluster, finding a workload in all of them, and what each card says.

Who you are, and what you can do

Your initials, at the bottom of the sidebar (at the top right of a fleet’s page of clusters), open a menu that shows who you’re signed in as, and your groups: four by name, then how many more. system:authenticated, which everyone signed in is in, isn’t listed. Where the name and groups come from depends on how you signed in:
  • With a token: the cluster’s own answer for that token. That’s exactly the name and groups the cluster applies roles to.
  • With single sign-on: what your provider says about you when you sign in.
  • Behind a company login: what the proxy passes on to Lumovi.
Your access comes from the roles bound to that name and those groups. With single sign-on or a company login, the cluster may know them with a prefix your team chose, like oidc:: then roles are bound to oidc:alice@example.com and oidc:platform, while the menu shows alice@example.com and platform. In a fleet, each cluster has roles of its own, and may use a prefix of its own.
Lumovi served from a cluster: who's signed in, and their groups.Lumovi served from a cluster: who's signed in, and their groups.

Who's signed in, and their groups.

  • Actions you aren’t allowed to take are turned off, with the reason, like “Your account can’t delete pods in shop.”
  • If you can only see some namespaces, pick one from the namespace menu, or type its name.
  • Your access, in the same menu, says what Lumovi’s admins let you do through Lumovi, and why: less than your roles allow, maybe, never more. Under your name, the menu lists the groups of Lumovi’s you’re in. Admins also have Admin. See Your access.
  • Sign out is in the same menu. Behind a company login, it signs you out of the proxy, if your team set that up. Otherwise the menu says Signed in by the proxy in front of Lumovi.

Good to know

A session lasts 12 hours unless your team changed that. When Lumovi restarts, after an upgrade say, you stay signed in: the page reconnects. When a session ends, you come back to the sign-in page, and land where you were. Behind a company login, Lumovi keeps no session of its own: the proxy decides when you sign in again.
A banner says Reconnecting to Lumovi…, and the page keeps what it showed. It picks up again as soon as the server answers. If it goes on, the server may be down, or a proxy in front of it may not pass WebSockets.
Your theme is kept in your browser. A cluster’s settings are the server’s, the same for everyone: whether it’s 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; the cluster switcher says who made a cluster read-only, and when. Read-only holds for everyone’s AI assistants too.
AI assistants and agents that speak MCP can use your team’s Lumovi as you. When you connect one, it opens Lumovi in your browser: sign in as usual, and Allow an AI assistant? asks whether it may act as you, and counts what it will be able to do with your permissions. Allow it only if you started this from the assistant it names. See AI assistants on a server.
Lumovi keeps an audit log of what’s done through it: your sign-ins and sign-outs, your changes, the shells you open, the logs and Secrets you read, and what your AI assistants do as you. You see your own events on the Audit log page; your team’s auditors see everyone’s. Values, like a Secret’s, are never in it.
Browsers keep ⌘N and ⌘1…6 for themselves. The command palette (⌘K, or CtrlK on Windows and Linux) has those commands. Everything else is the same as in the desktop app.

Take the tour

Five minutes through the app’s main ideas.

Changing things safely

What Lumovi checks before it changes anything.