See
See your entire cluster.
Health, workloads, dependencies, network and cost in one place.
All green. Until it isn't.
How KubeBolt works
We follow a Kubernetes incident from start to finish: what detects it, what the model reads, what it may touch and what is written down by morning.
1.70 req/s · 2xx 0.85/s · 5xx 0.85/s · avg latency 68.4 ms
Liveness probe failingWARNING
Pod payments/payments-api-7f8d4-xk2m liveness probe has failed 6 times.
Suggestion: Check the liveness probe config against what the app actually does at startup.
Zero Available ReplicasCRITICAL
Deployment payments/payments-api has 0 available replicas.
Pod not passing readinessWARNING
Pod payments/payments-api-7f8d4-p2kq is Running but has not been Ready for over 2 minutes.
Conditions firing right now · 24 rules
Deploymentrevision 43 · 8m ago
Pods7 restarts
Metricserror rate +18.7%
Networkpayments path degraded
Eventsliveness probe failed
Logs3 relevant errors
Six sources correlated on the same workload. Without leaving this screen.
Pods (26) · rolling update · reversible
rollout complete · 26/26 ready
liveness probe passing · 90 s straight
error rate back to baseline
today · 87 sthis one
6 days ago · 13 mauto_recovered
20 days ago · 4 mauto_recovered
If any of the three fails, it reverts and escalates the incident to you.
From signal to resolution, with nothing to reconstruct along the way.
See
Health, workloads, dependencies, network and cost in one place.
All green. Until it isn't.
See
Deterministic rules surface what is broken and what is about to break, each with a concrete recommendation. Not an alert — a finding with a name.
24 rules in production. The one that fires most: the liveness probe.
Understand
KubeBolt correlates the deployment, restarts, metrics, traffic, events and relevant logs into one operational context. Kobi reasons over that context to find the cause.
KubeBolt builds the operational context. Kobi reasons over it.
Understand
Kobi reasons over that context, already built: it doesn't go looking, it already has it. That's why it gets there fast — and why you can follow every step.
The intelligence doesn't come from the model. It comes from the context in front of it.
Act
The operations you already know, one click away, with your RBAC. Or Kobi proposes the action, validates it against the cluster and shows you what will happen before touching anything.
KubeBolt is still an operations platform even if you never enable autonomous mode.
Act
The action comes from a closed catalog and the rollout is visible pod by pod, with live ready and updated counters.
This is production changing in front of you.
Verify
KubeBolt doesn't call an action good because it finished: it checks that the probe passes, that the error rate is back to baseline and that the workload holds. If it doesn't, it reverts.
And it keeps the episode, with the previous ones. Three with the same fingerprint is no longer bad luck.
From signal to resolution, with nothing to reconstruct along the way.
02 · The six layers
24 rules watch your Kubernetes cluster state: crash loops, OOM, images that won't pull, expiring certificates. Nothing to configure and no credits spent.
100% deterministicClassifies what was detected and decides whether it needs investigating. This is where credits start to count.
AICross-checks events, logs, metrics and recent changes until it finds the cause.
AIWrites the plan. If confidence doesn't reach the rule's threshold, it stays a suggestion.
AIApplies only what passes the guardrail. The plan is validated against code, not against a prompt.
AI + deterministicLeaves the timeline, the evidence and a draft analysis.
AIEach rule is a Skill: it carries its confidence threshold and says which catalog actions are valid for that incident. If it isn't in the catalog, the finding still arrives, with its recommendation, and you resolve it.
03 · How far it goes
Tools run in the backend and the model only sees results. Before touching Kubernetes production, every action goes through code the model can't change.
If a step isn't on the list, the plan is rejected and escalates to a person.
Changing the prompt doesn't widen the catalog.
Logs are text a third party may have written. That's why the model proposes.
It runs with a Kubernetes ServiceAccount and is audited: who authorized it, when and on which resources.
Days, hours and timezone. Outside it, the incident is logged and nothing acts.
BYOK on OSS and EE Self-Hosted: your key or endpoint, and AI traffic goes from your install to your provider. On SaaS, AI is managed. Autonomy levels
Try it
A closed action catalog and your cluster's RBAC. The only thing that changes is who approves.
three get resolved · one reverts · one stays out
Kobi diagnoses, shows you the exact command and runs it on your click. Destructive actions always carry your signature.
Illustrative script using actions from the real catalog.
Break something and watch where the action goes.
04 · Verify and revert
Applying isn't resolving. Autopilot saves the previous values before touching anything, then checks the result. It works today.
The values it will change are captured first, so the revert restores exactly what was there.
Pods Ready and no restarts. It isn't enough for the action to apply without an error.
The episode is saved with the previous ones, in case it comes back.
In autonomous mode it undoes itself. A rollback that needs approval waits for you.
With what was tried and why it didn't work. That's the honest ending when the catalog falls short.
Postmortem · L6
The last step fixes nothing: it tells the story. Ready to paste into the channel or the ticket.
Sample, using the incident on this page.
The timelineFrom the first signal to the last Ready pod.
The action logIn autonomous mode it's signed by Autopilot.
patch_probepayments/payments-apiappliedAutopilot
The five whysThe model writes it, you sign it.
05 · What you install and what you don't
The four answers a platform team asks for before installing anything in production.
Outbound gRPC channel from inside the cluster. Your API server is never exposed: no VPN, no bastion, no open ports.
No kubeconfig on the operator's laptop. Start with metrics or read-only and move up to operator whenever you want.
If you have it, it's joined to resources, events and changes. If not, the agent uses kubelet metrics.
Only what's needed to investigate leaves the cluster. What is sent, how long it's kept and where, in the trust model.
YOUR CLUSTER · EKS, GKE, AKS, OPENSHIFT OR ANY KUBERNETES
KubeBolt agent
ServiceAccount · no kubeconfig
RBAC: metrics ▸ read ▸ operator
starts read-only
API server
not exposed · no VPN
Prometheus
yours, if you have one
workloads · events · logs · changes
YOUR NETWORK · FIREWALL
KubeBolt Cloud
or self-hosted on your infra
The channel
→Leaves
✕Never crosses
On self-hosted nothing reaches KubeBolt: no product telemetry, no usage ping. Trust model
Why the other way round
| Traditional modelLens · Kite · K9s · direct kubectl | KubeBoltThe agent dials out, nothing comes in | |
|---|---|---|
| API server | Reachable from the client | Stays private, never exposed |
| Credentials | On every user's machine | Only in the agent, with a ServiceAccount |
| Private clusters | VPN or jump host | Private GKE and EKS, isolated VPCs |
| Audit | In the cluster, not centralized | Centralized in the control plane |
Where the metrics come from
How much is kept
Around 1 GB per 100 pods at 30 days. Cardinality decides, not days. On self-hosted it's a value in your Helm chart. Detection rules don't depend on retention. See the plans
06 · Also, the panel
$kubectl exec -it Multi-pod and multi-cluster, with no kubeconfig on the client and no VPN.
$kubectl exec -- ls What's in the pod now, not what shipped in the image.
$kubectl logs At workload level and on demand, without waiting for your stack.
$kubectl port-forward Grafana or ArgoCD with no public LoadBalancer or Ingress.
$kubectl edit · scale · rollout With validation and CRDs. Deleting Namespaces, Nodes, PV, PVC or RBAC is vetoed by design.
$kubectl config use-context One agent per cluster, all in the same control plane.
Autopilot already verifies every fix and reverts it if things get worse. What's coming is having it written in your repo, where the truth lives.
Before opening a PR we confirm that file produces that workload. Your checks and branch protection rule.
“KubeBolt is a Kubernetes operations platform: one place to see, understand and operate your clusters, and Kobi works from that same context. The UI is excellent, but the product is two pieces: the Core (API), home to the correlation engine, and the agent that brings it the facts without exposing anything.”
Leafar Maina · Founder, CLM Cloud Solutions
Cloud
Create the account, install the agent, and on the first alert you'll see Kobi working with you. Start in suggest-only.
Free · 2 clusters · no time limit
Example · the app generates it with your token docs
helm install kubebolt-agent \
oci://…/helm/kubebolt-agent \
… --set cluster.name=<cluster-name> Rather see it with a person? Book 20 minutes
Open source on your cluster
Install KubeBolt on the cluster you want to monitor. The agent is added from inside the product.
$ helm install kubebolt \
oci://ghcr.io/clm-cloud-solutions/kubebolt/helm/kubebolt \
--namespace kubebolt --create-namespace --wait Apache 2.0 · ★ on GitHub · the agent dials out, never in.
What's next
One note per release, no noise.
Create the account
Free, 2 clusters, no time limit.
Install the agent
One helm command. The wizard generates it with your token.
Your cluster shows up
And Kobi starts watching it, in suggest-only.
<cluster-name> · connected
The KubeBolt AI SRE · visiting
Kobi can be wrong. Official pricing lives in the plans section.