The KubeBuddy Tools

KubeBuddy CLI

The scanning tool for Kubernetes and AKS. Run it locally, in Docker, on a jump host, or in CI to generate HTML, JSON, and terminal reports.

• Deep cluster, workload, security, and AKS checks.
• No agents or in-cluster install required.
• Works as the execution layer for the whole workflow.

CLI Docs PowerShell

KubeBuddy Radar

The hosted service for tracking CNCF and cloud-native project releases, getting alerts when new versions land, and reviewing AI-improved release notes.

• Track projects, releases, and changes across the cloud-native ecosystem.
• Get alerts when new releases happen and route them to the right teams.
• Use Cluster Reports and Cluster Configs when you want KubeBuddy scan history too.

Open Radar ↗ Radar Docs

Why Teams Use KubeBuddy

CLI First

Run the scan where your cluster already lives.

Use PowerShell or Docker to scan Kubernetes and AKS without installing agents, Helm charts, or in-cluster components.

• Generate HTML, JSON, and terminal output from the same run.
• Pull Prometheus metrics when available for richer diagnostics.
• Run locally, in CI, in Docker, or from a jump host.

Built For Action

Get findings you can actually work with.

KubeBuddy is designed to move from detection to action fast, with clear reports and consistent checks across clusters.

• Catch node, pod, workload, RBAC, network, and storage issues in one pass.
• Run AKS best-practice checks when you need provider-specific coverage.
• Keep the cluster untouched while you inspect it from outside.

What KubeBuddy Checks

Node And Pod Health

Find crash loops, failing workloads, noisy nodes, broken probes, and cluster drift before they become outages.

Security And RBAC

Catch risky RBAC, exposed privileges, insecure defaults, weak registries, and config mistakes that stay hidden in dashboards.

Networking, Storage, And AKS

Inspect services, PVCs, policies, cluster config, and Microsoft-guided AKS checks from the same workflow.

🤖

Clear Guidance, Not Just Raw Findings

Use the CLI to surface the findings fast, then review the HTML and JSON reports to decide what changed, what matters, and what to fix first.

Optional KubeBuddy Radar Workflow

Radar Integration

Bring scan history into the same place you track releases.

Upload KubeBuddy JSON reports into KubeBuddy Radar when you want score history, compare views, saved scan profiles, and one place to manage both releases and scan results.

• Compare runs over time and across clusters.
• Manage encrypted scan profiles and generated commands.
• Keep scans local while Radar handles release tracking, history, and coordination.

Use It When Needed

KubeBuddy still works fully on its own.

You do not need Radar to run scans, generate reports, or work through findings. Radar is the optional control plane for teams that want more history and compare.

• CLI-only workflow stays simple and self-contained.
• Radar adds run history, compare, and config management.
• Choose the level of workflow you need.

How The KubeBuddy Workflow Fits Together

⚙️

Run KubeBuddy Locally

Scan from your terminal, jump box, CI job, or Docker container using your existing kubeconfig and provider access.

CLI first

🔎

Generate A Report

Keep the HTML locally for deep inspection and use the JSON for automation or optional Radar uploads.

HTML + JSON

📈

Optionally Track It In Radar

Review score trends, compare reports, and manage config profiles so future scans are consistent across your clusters.

KubeBuddy Radar

Read the CLI Docs