Skip to content

Kubernetes says your cluster is healthy. It’s probably not.

Why KubeBuddy?

πŸ”

Comprehensive Diagnostics

Detects node failures, pod crashes, security risks, and networking issues with one command.

πŸš€

No Cluster Intrusion

Runs externally via your terminal or Docker, requiring no agents or Helm charts.

πŸ“Š

Actionable Reports

Export detailed HTML, JSON, or CLI summaries for quick insights and sharing.

πŸ›‘οΈ

Clean Execution

KubeBuddy runs entirely outside your cluster. No agents, no config drift, no exposure.

πŸ§ͺ

Stateless by Design

Scans don't persist anything. No runtime footprint, no security baggage.

⚑

Runs Anywhere

Use it locally, in CI/CD, or on a jump host β€” wherever you work.

What KubeBuddy Checks

Node & Pod Health

Identifies failed nodes, pending pods, and crash loops.

Security Risks

Scans for risky roles, excessive bindings, and exposed permissions.

Networking & Storage

Checks PVCs, services, policies, and reachability issues.

AKS Best Practices

Runs Microsoft-guided checks with a single flag.

Cluster Config

Checks context, kubeconfig, versions, and misaligned settings.

Resource Limits

Flags containers missing CPU or memory limits. Prevent noisy neighbors.

How KubeBuddy Works

βš™οΈ

Connect & Scan

KubeBuddy uses your existing kubeconfig to scan your cluster externally, no agents required.

πŸ”Ž

Analyze Issues

Detects hidden problems like misconfigurations, security risks, and resource failures in seconds.

πŸ“ˆ

Deliver Insights

Generates clear, actionable reports in HTML, JSON, or CLI format for immediate action.