Kubby
Features

A Kubernetes GUI with everything in one window

Real Kubby screens on test data. Every feature is free for everyone.

Problems first

Pods, Events and the Overview put CrashLoopBackOff, OOMKilled and ImagePullBackOff at the top, not on page four of a table.

Counts on every resource kind and on every cluster in the rail tell you where to look.

Learn more
Pods: 15 that need attention pinned at the top, CrashLoopBackOff, ImagePullBackOff and ContainerCreating with their restarts

The cluster and every node at a glance

Ready nodes, running pods, warnings of the last hour and the CPU and memory of the whole cluster at the top of the Overview.

Pick a node to see its CPU and memory over the last hour, its disk, pods and versions. The node table shows CPU, memory and disk for all of them, and which one is under pressure.

Learn more
Overview: worker-03 under memory pressure, its CPU and memory over the last hour, disk at 61% and 57 of 110 pods

A health score for every cluster

A grade from A to F and a score out of 100 for workloads, pods, nodes, network, storage and security, with a 30-day trend.

Fix first lists what costs the most points: no memory limit, images without a fixed tag, containers running as root, services without endpoints. Accept the ones you keep on purpose, with a reason.

Learn more
Cluster health: grade B, 87 of 100, scores per area, findings by rule and scores per namespace

Why is it restarting?

Kubby answers in one sentence: exit code, memory peak against the limit and the restart pattern.

The logs before the crash are one click away.

Learn more
Pod details: OOMKilled, peak 517Mi of the 512Mi limit, restarts every 5 minutes

Ask Kubby

Connect Claude, ChatGPT, Gemini, Grok or your company's AI gateway with your own account. It reads the cluster through Kubby's read-only tools.

It explains the cause with the evidence and proposes a change for your review.

Learn more
Ask Kubby: the pod is OOMKilled at its 512Mi limit; a change to 768Mi is proposed

Changes you review first

Every proposal and every YAML edit shows a diff before it is applied with server-side apply.

On a PROD cluster you type the cluster name to confirm.

Learn more
A proposed change as a diff: memory limit 512Mi to 768Mi, confirmed by typing the cluster name

Logs before the crash

Live and previous logs of a pod or a whole workload, with levels, search and a restart history above.

Pick the crashed run and read the last lines before it died.

Learn more
Pod logs with the restart history, INFO and WARN lines and the previous run

All the pods in one timeline

Pick deployments, labels or whole namespaces: the logs of every pod and container run in one live timeline, with pod starts, kills and events between the lines.

Log volume, levels, the busiest pods and the restarts on top; one click jumps to the crash.

Learn more
Logs page: 33 pods of a deployment in one live timeline with log volume, levels, pods and restarts

Logs of pods that are already gone

History searches Loki, Elasticsearch or OpenSearch, found in the cluster or added once as a central store, so the logs of deleted pods and the node's kubelet and containerd logs are still there.

Passwords stay in Kubernetes Secrets you create; Kubby keeps only the reference.

Learn more
Logs history from the cluster's Loki: 24 hours from 6 pods that are gone from the cluster

No actions on the wrong cluster

Environment colours on every screen, and the cluster name typed before scaling, deleting or rolling back on PROD.

Everything you change is written to the audit log.

Learn more
Scaling a Deployment on a PROD cluster asks for the cluster name

Monitoring, already set up

Kubby finds the cluster's Prometheus and shows capacity, workloads, control plane, etcd, storage, network and certificates.

Ranges from 5 minutes to 7 days.

Learn more
Monitoring: capacity gauges and CPU used, requested and limited

Logs and metrics, set up for you

A cluster without a log store or Prometheus gets an offer: Loki with Alloy, or a small Prometheus, from your private registry if you have one.

Before anything is installed you see the CPU, memory and disk it uses on your nodes, the rights it needs and the images. You approve it, it is audited, and Kubby connects to it.

Learn more
Set up logs: CPU, memory and disk for Loki and Alloy on 10 nodes, the rights needed and the images

Node health at a glance

Nodes ready, average CPU and memory, the fullest disk and nodes under pressure.

Click a node for its disks, OS, kernel, uptime and heaviest pods.

Learn more
Monitoring, Nodes tab: 10 of 10 ready, fullest disk 93% on worker-03

Argo CD control centre

All your Argo CD instances in one place: health and sync charts, sync activity, the cluster map and projects.

Works with the Argo CD API, so the instance can run anywhere.

Learn more
Argo CD overview: 23 applications, health and sync rings, sync activity and the cluster map

Why an app is Degraded

Applications with filters for what needs attention, and the reason behind a Degraded state.

Diff, history, rollback, sync and auto-sync from the same panel.

Learn more
A Degraded Argo CD application: the pod in ImagePullBackOff behind it

Helm with the full history

Releases across namespaces with chart and app versions, a newer-version badge and status.

Values, upgrade to another version, revision compare and rollback.

Learn more
Helm releases: chart and app versions and status of each release

Rollout history and rollback

Every revision of a Deployment with its image and age.

Roll back to a revision in one click, after a confirmation.

Learn more
Rollout history of a Deployment with three revisions and Roll back buttons

Command palette

Ctrl+K reaches every resource, page and action, in this cluster or the others.

Keyboard shortcuts on every screen.

Learn more
Command palette: resources, actions and the other clusters for the search 'scale'

A terminal in the right context

PowerShell, cmd or WSL with the cluster's kubeconfig loaded and the namespace set.

Pod shells and port forwarding from the same place.

Learn more
A terminal opened on a PROD cluster in the default namespace

News for what you actually run

Security patches and new versions matched to the components in your cluster: ingress-nginx, RKE2, Kubernetes, Argo CD.

Prometheus alerts in the same bell.

Learn more
Notifications: a security patch for ingress-nginx and RKE2 and Kubernetes upgrades

Who changed what, and when

Every apply, scale, restart, cordon, delete and secret reveal with the user, cluster, object and result.

Filter by user, action or object.

Learn more
Audit log: time, user, cluster, action, object and result of every change

Every cluster, grouped

Import kubeconfigs, group clusters by environment and colour, and see which ones have problems.

Unreachable clusters say why.

Learn more
Clusters grouped as Production, Pre-production, Test and DR with problem counts

Events that explain

Warnings first, grouped by reason, live, with the object they belong to.

Last hour or last day in one click.

Learn more
Events: BackOff warnings with the pods they belong to

Kubby works with any Kubernetes cluster

RKE2 and Rancher, k3s, kind and every distribution that speaks the standard Kubernetes API. Nothing required on the clusters: Kubby uses your kubeconfig and your RBAC.

  • RKE2 / Rancher
  • k3s
  • kind
  • Prometheus
  • Argo CD
  • Helm
  • WSL and PowerShell
Download

One app, built for Windows

Windows 10 and 11, 64-bit. Free, with every feature. Installs per user without administrator rights.

Download for Windows Release notes