What is KubeGraf?

Why this matters

Most engineers meet Kubernetes through production incidents, not conference talks. When a cluster is on fire, you don’t want to hand‑assemble kubectl one‑liners and mentally stitch logs, events, and dashboards together. KubeGraf exists to give you a single, AI‑aware control plane for understanding “what’s going on in this cluster” in seconds instead of minutes.

Info: Think of KubeGraf as a local‑first control plane that sits on top of the same kubeconfig and RBAC you already use with kubectl, not a replacement for it.

What KubeGraf actually is

KubeGraf is a local-first, Intelligent Insight for Kubernetes Incidents that gives you three ways to work with your clusters:

  • Terminal UI – a fast, keyboard‑driven TUI (kubegraf) that feels like k9s with better navigation and context.
  • Web dashboard – a browser UI (kubegraf --web) with cluster topology, incident timelines, and live event streams.
  • SPA dashboard – the hosted SPA at kubegraf.io that mirrors the same concepts for teams who prefer the browser.

Real‑world example: “What is wrong with payments right now?”

Imagine you’re on‑call for the payments namespace. SRE pings you: “payments API is 500’ing in prod-cluster.”

kubectl config use-context prod-cluster
kubectl get pods -n payments
NAME                                   READY   STATUS             RESTARTS   AGE
payments-api-66cbd9d4dc-7xg9n          0/1     CrashLoopBackOff   5          2m31s
payments-api-66cbd9d4dc-87zc2          1/1     Running            0          5m12s
redis-payments-0                       1/1     Running            0          10m

What you actually care about:

  • What changed in the last 10 minutes?
  • Is it just this one pod or the whole deployment?
  • Is there a config / secret / image mismatch?

KubeGraf lets you:

  • Open the Terminal UI with kubegraf.
  • Jump to payments and see CrashLooping pods highlighted.
  • Open the Incident Timeline to see deploys, config changes, and failing probes together.
  • Ask the Brain Panel for a proposed root cause based on events and logs.

Tip: Always check kubectl config current-context before launching KubeGraf so you don’t debug the wrong cluster.

Screenshot placeholder

[ screenshot: cluster overview with highlighted CrashLoopBackOff pods in the payments namespace ]

Expected outcome

After this page you should:

  • Understand what KubeGraf is and how it plugs into your existing kubeconfig and tools.
  • Be ready to launch KubeGraf and scan a real cluster without changing any manifests.
Previous
First Cluster
Next
Terminal UI