Getting started
Install the agent, connect your first cluster, and see recoverable spend in under five minutes.
KubeHero is a unified cost and efficiency plane for AKS, GKE, and EKS. This page walks you through the fastest path from zero to "I can see which pods are wasting money."
Prerequisites
- A Kubernetes cluster running 1.28 or newer
kubectlauthenticated to that clusterhelm3.x (for the Helm install path) or no tools at all (for KubeHero Cloud)
Install the agent
helm repo add kubehero https://charts.kubehero.io
helm install kubehero kubehero/kubehero \
--namespace kubehero-system --create-namespace \
--set cloud.enabled=true \
--set cloud.token=$KUBEHERO_TOKEN
That's the whole install. The agent runs read-only by default — no write permissions on your workloads.
Confirm telemetry is flowing
kubectl -n kubehero-system get pods
kubectl -n kubehero-system logs daemonset/kubehero-collector --tail=20
You should see attribution ok · pods=NNN · nodes=NN within 30 seconds. If not, see Troubleshooting.
Your first scan
The CLI works against both the Cloud and Self-Hosted control planes:
kubehero cluster list
kubehero scan --cluster prod-us-east-1 --report waste
A minute later you'll see the top wasting workloads ranked by recoverable $/mo.
What's next
- Architecture — how the pieces fit together
- CRD reference —
BudgetPolicy,CeilingPolicy,RightsizingPolicy - CLI reference — every subcommand, every flag