返回资讯中心
外部精选
软件工程
#开发者实时流

Kubernetes Dashboard – Lumovi

RunningVersion 1.22.1 is out Your clusters,at a glance.

Hacker News 最新kotapeter2026/10/17 · 2026/10/1730 分钟阅读

以下正文同步自 Hacker News 最新,版权归原站所有,已转换为易读排版。

RunningVersion 1.22.1 is out Your clusters,at a glance.

Lumovi is a calm, fast Kubernetes dashboard, on your desktop or in your cluster. It shows what’s healthy, what’s struggling and where your capacity goes, for you or your whole team, from one cluster to a fleet.

Hover a pod. Click a failing one to restart it.Tap a pod. Tap a failing one again to restart it.Everything’s running. Nice work.

The tour: every part of Lumovi, in 10 minutes →

Lumovi reads your kubeconfig and asks each cluster’s API server for its version, so you see which ones answer, how fast, and which don’t. A cluster that signs in through a program, as the clouds’ do, waits until you open it, so nothing opens a browser at launch. Paste a kubeconfig to add a cluster: Lumovi keeps it, and never writes yours. Give each one a name, a color and a group, and switch with ⌘K from anywhere.

Search clusters and labels…5 of 5 Group by Add cluster

Lab2

Llegacy-onprem10.20.0.15:6443 · admin

Shop3

PUProduction USProductionprod-us-east

SEStaging EUstaging-eu

to move to open.for actions⌘Nto add

Connect your clusters

The appOne calm window for every cluster you have.

Pick a cluster and Lumovi shows you how it’s doing. Problems sort to the top, usage sits next to capacity, and the details are one click away. It follows your system’s light or dark, and every status has an icon and a label, never color alone.

What needs attention, live usage against what’s allocatable, and every node’s load. Overview

Deployments, StatefulSets, DaemonSets, Jobs and CronJobs in one list. Failing ones first. Workloads

Pick a few rows, or a hundred, and restart or delete them together. Several at once

History from your Prometheus or VictoriaMetrics, found for you. Drag across a chart to zoom. Usage history

Releases, their values and every revision, with a diff between any two. Helm releases

What each workload should request, from a week of its use. Checked by the API server first, with undo. Usage history

Every pod of a workload, merged in the order lines were written. Logs

A shell on any node, as root, or in any container, with a debug container for pods that have none. Shells on nodes

On the desktop, your own shell along the bottom, pointed at this cluster, with a kubectl that matches it. Terminals

Each tool the cluster runs gets a page. Karpenter’s: node pools against their limits, and who’s waiting. Included plugins

Press G then a letter to switch views, just like in the app. Every shortcut

Every object has a map: what leads to it, from the gateway and routes to the services and policies in front of it, and what it uses, from its pods and the ConfigMaps and Secrets they read to the nodes they run on. Point at anything to trace its chain. What’s missing or unwell takes its color, so you see it first.

Deployment · shop · 88d oldstorefront Ready Scale Restart

Above it, what leads to it; below, what it uses.Routes, ownsUses

Secret shop-tlsMounted by its pods, but not there Not found

Node worker-2Runs one of its pods MemoryPressure

Object details

Change things safelyEvery change shows its kubectl. Any revision, one rollback away.

checkout has crash-looped since its last rollout. Roll it back to the revision before, and watch its pods come up one by one. Lumovi checks your permissions first.

Roll back checkout

Deployment · shop · demo

Roll back

Changing things safely

CapacitySee where your capacity goes. And why a pod can’t start.

Each node as the scheduler sees it: what its pods request against what it can give, and what they really use. When a pod waits for room, you can see there isn’t any. Right-sizing then says what each workload should request, from a week of its use.

worker-2Used 86% · 6.3 GiB of 7.3 GiBUsed 48% · 1.9 cores of 3.9 cores

Pod · data · 0/4 nodes are available: 1 node(s) were not ready, 3 Insufficient memory.

Live usage

FeaturesMade for the day something breaks. Calm on all the others.

Problems sort to the top

Every object gets a clear status, and whatever is failing comes first, as the cluster changes. You won’t scroll past 400 healthy pods to find the one that isn’t.

Health and status

NameTypeStatus Pods

db-migratebatch Job Failed0/1 done

recommendationsshop Deployment Unavailable0/1

checkoutshop Deployment Degraded1/3

redisdata StatefulSet Degraded1/2

backfillbatch Job In progress0/1 done

cartshop Deployment Ready2/2

corednskube-system Deployment Ready2/2

grafanamonitoring Deployment Ready1/1

Helm releases, read in place

Status, values, what it made and every revision, with a diff between any two. Upgrade, or install from Artifact Hub or your computer: a dry run first, then the helm Lumovi brings.

Helm releases

3Upgrade completeChart 2.4.1 · app 3.9.1 · 2d ago Deployed

2Upgrade completeChart 2.4.0 · app 3.9.0 · 20d ago Superseded

1Install completeChart 2.3.0 · app 3.8.0 · 60d ago Superseded

From21To3valuesmanifest

⌘K goes anywhere

Jump to any page, object, namespace or cluster. Every page has a shortcut, and what you pin is a key away. Try it.

Finding things

to move to selectesc to close

A workload’s pods merged in the order they wrote, each line marked with its pod. Pods that start later join in. Keep only errors, leave a pod out, search with a regular expression, or read a crashed container’s last run.

Logs

Errors 4Warnings 29hqnnn 19lnk52 242pwkd2 19

AI assistantsDesktop, server and fleetYour assistant, with you in charge.

Lumovi is an MCP server, so any AI assistant or agent that speaks MCP can work in your clusters through it, on your desktop or your team’s Lumovi, as you. You say what they may do, down to the namespace. What they want to change is checked by the cluster, then waits for your answer, with the diff, their reason and the kubectl that does the same.

AI assistants

Your assistantlumovi, over MCP

›

Your assistant asksScale Deployment storefront to 5 replicas

Deployment · shop · demo

WhyCheckout latency is up 40% since 9:00; storefront pods are at 95% CPU. Two more replicas spread the load.

Approved: checked again, and made. Rejected: nothing changed. Expired: nothing changed. Again

PermissionsA ruleActivity

Defaults for what assistants may do with changes, Secrets, env values and logs, and rules for some clusters and namespaces, the strictest winning. On a server, administrators set limits nobody loosens. What assistants may do

A rule matches namespaces by name, pattern or label, so one covers thousands. This one keeps assistants from changing data, its Secrets and its logs. What assistants may do

Every change an assistant asked for, made or rejected, and whose it was, with the command that does the same. Approving changes

Made as you saw it

Approved, a change is tried again, and made only if it still does what you saw. Deleting needs the name typed wherever Lumovi’s own Delete does.

Never more than you

Your RBAC first, then your rules: a namespace a rule hides isn’t there for assistants, and sensitive env values stay hidden unless you show them.

Signed in as you

On a server, it signs in through Lumovi, as you, with nothing to copy. On the desktop, it has a token kept where only you can read it.

Set up in a moment

On the desktop, a click or a command, whichever your assistant takes. On a server, any MCP client at its address, /mcp.

Install the Helm chart and Lumovi runs in the cluster, as a dashboard your team opens in a browser. Nobody installs anything, and everyone sees and changes only what their own permissions allow.

Install the chartRead the docs

JaneWith single sign-on

SamThrough the proxy

SupportWith a token

Signed in as[email protected]platformon-call

Your accessWhat you may do, and why

Sign out

Jane can see and change every namespace.

Your accessWhat you may do, and why

Sign out

Jane can see and change every namespace.

Your accessWhat you may do, and why

Signed in by the proxy in front of Lumovi.

Sam can change shop. They can only look at data, monitoring.

Your accessWhat you may do, and why

Sign out

Support can only look at shop, batch.

With a token

auth.mode: token

People paste a token the cluster accepts, a service account’s or one from your identity provider, and the cluster checks each request made with it. Lumovi’s own service account needs no permissions.

With single sign-on

auth.mode: oidc

Dex, Keycloak, Okta, Entra ID, Google or GitLab. Lumovi acts as whoever signs in, or passes their own token on when the API server already trusts the provider.

Behind a proxy

auth.mode: proxy

oauth2-proxy or Pomerium signs people in and names them in a header. The chart’s network policy keeps out everything but the proxy.

Every page has an address. Send someone the pod, its logs or the release you’re looking at.

Never more than each person’s own RBAC, their shells on nodes and AI assistants too, and readOnly: true keeps everyone from changing anything.

A small image for amd64 and arm64 that runs as non-root, has no shell and writes only to /tmp.

One Lumovi in a browser for all of your clusters. Each is summed up the way its overview would, what needs attention comes first, and everyone sees each cluster as their own RBAC there allows.

Each cluster summed up as its overview would, what needs attention first, and its labels to filter and group by. A fleet of clusters

A workload by its name or namespace, in every cluster at once, and open where it runs. Clusters in a fleet

Each person’s own RBAC

mode: member

Lumovi acts as whoever signs in, with single sign-on or a proxy, or passes their own token on to clusters that trust your identity provider. Their AI assistants act as them too.

Private clusters too

mode: agent

An agent in the cluster dials out to Lumovi. Nothing in it listens, no firewall lets anything in, and TLS runs to the API server through it.

Clusters found for you

LUMOVI_FLEET_KUBECONFIG

From a kubeconfig, or the Secrets Cluster API and Argo CD already keep, with each one’s labels and who may see it.

PORT

In a cluster with the Helm chart, on a VM, or on a platform like Sevalla from the image, with every setting in its environment.

Admins decide who may do what through Lumovi, team by team: developers change their own namespaces, on-call fixes production, contractors look but don’t touch. Never more than Kubernetes RBAC allows, and everyone can see what they may do, and why. What’s done through Lumovi is recorded: by whom, from where, and how it went.

Access for your team

GroupsProfilesGrants and limitsCheck someoneYour accessAudit log

Groups from your identity provider, such as Okta, Microsoft Entra ID, Google or Dex, or people by name. Joining or leaving a team there carries over here. Access for your team

What someone may do, as a set: changes, shells, node shells, logs, Secrets (hidden, keys or values), Helm, AI assistants and the audit log. What shows Secret values or runs code on nodes stands out. Access for your team

Grants give a group a profile in some clusters and namespaces, by name, pattern or label. Limits hold anyone back wherever they match, whatever grants give. Access for your team

Anyone, anywhere, checked before you save, with the rule that decides each answer. Changes are saved together, and recorded in the audit log with what they were before. Access for your team

Everyone sees what they may do, cluster by cluster, and why. The server decides, not the page: what it refuses, someone or their AI assistant, says why, and links here. Your access

What was done through Lumovi, by whom, from where, and how it went. Each event is chained to the one before it, and Lumovi can check that the history holds together. The audit log

Admins you name

LUMOVI_ADMINS

Groups or people, named in the server’s settings, never on the page. With none, nothing changes: everyone may do what their RBAC allows.

Kept in Git, if you like

access.policy

The Helm chart can set the admins and the rules, for tea

正文由 探How 从来源站点 RSS 同步,内容未经改写;遇到排版缺失或需要图片、视频时请以原文为准。

打开原文
去社区讨论 →