Changelog

​

The first version of Lumovi

​

Two ways to run it

• On your desktop. An app for macOS, Windows and Linux that opens every cluster in your kubeconfig, with client certificates, tokens and credential plugins found on your login shell’s PATH. It updates itself: new versions download in the background and install when you restart or quit. Help → Check for Updates… looks right away.
• In your cluster. A container image, ghcr.io/lumovi/lumovi for linux/amd64 and linux/arm64, and a Helm chart serve the same app as a dashboard your team opens in a browser. People sign in with a token the cluster accepts, with single sign-on (OpenID Connect), or through an authenticating proxy, and see and change what their own RBAC allows. Every page has an address you can share.

helm install lumovi oci://ghcr.io/lumovi/charts/lumovi \
  --namespace lumovi --create-namespace

​

Seeing what’s going on

• Overview with node, pod, workload and warning health, CPU and memory against capacity, and what needs attention.
• Lists for every kind, with health, sorting, filters and label selectors. Big lists load in chunks and stop at 5,000 objects, so huge clusters stay fast.
• Workloads of every kind in one list, pods that nothing manages included, with status, ready pods, autoscaler ranges and usage.
• A detail panel next to the list, with kind-specific facts, containers, conditions, events, logs and YAML. Secret values stay hidden until revealed.
• Map, a tab on every object: what leads to it, from gateways and ingresses to services, and what it owns, uses and runs on, down to the nodes. What’s missing, and what nothing uses, stands out.
• Logs streamed as they’re written, one pod’s or every pod’s of a workload merged by time, with search and filters.
• Usage history from Prometheus or VictoriaMetrics, found for you: a Metrics page that ranks namespaces, workloads, pods and nodes, and a Metrics tab on pods, workloads and nodes.
• Right-sizing, a tab of Metrics: what each Deployment, StatefulSet and DaemonSet should request, from a week of its usage, and why. A recommendation is applied once the API server has checked it, with undo.
• Helm releases, read from where Helm 3 and 4 keep them, with values, the objects they made, notes and diffs between revisions.

​

Custom resources, views and add-ons

• Every kind the cluster serves, found through API discovery, with the columns kubectl get prints and a status read from their conditions.
• Views describe a kind’s columns, status, details, links, related objects and actions as data. Lumovi ships its own, and yours in ~/.lumovi/views add to them or replace them.
• Add-ons give each tool the cluster runs an entry in the sidebar, with everything of its kinds in one list, failing first. Lumovi has add-ons for 32 tools, from Argo CD, cert-manager and Flux to Istio, KEDA and Velero.
• Karpenter’s add-on opens on an overview: node pools against their limits, the nodes they launched, what’s being disrupted and why, and the pods waiting for a node.

​

Changing things

• Actions to scale, restart, change images, roll back, pause and resume rollouts, run CronJobs, suspend and resume, cordon, uncordon and drain, evict and force-delete, change autoscaler ranges, expand volumes, and edit labels, annotations and YAML.
• Shells and debug containers, and port forwards on the desktop.
• Helm upgrades and installs, reviewed as a server-side dry run first, and rollbacks and uninstalls, all with your own helm.
• Bulk actions with progress per object and a retry for failures, and create from YAML with templates, checked by the cluster before anything is created.
• Guard rails: permission checks, the kubectl command in every dialog, typed confirmation for risky deletes, undo, an activity log and read-only mode.

​

Around the app

• A command palette, keyboard shortcuts, a native menu with the same commands, and light and dark themes.
• Calm errors: a banner when a cluster stops responding, the last data kept on screen, and error pages with details to copy or report.