How KorPro Works

Get started with Kubernetes resource optimization in 5 simple steps

1

Get Your License Key

Sign in to KorPro and go to Settings → Inspector. Copy your license key — the page shows ready-to-run install commands with your key already filled in.

  • Free tier available — no credit card
  • License key gates API access
  • Manage all connected clusters from one dashboard
  • Rotate keys anytime from Settings
2

Deploy the Inspector

Install the KorPro Inspector into each cluster with a single Helm command. RBAC, ServiceAccount, Secret, and a CronJob are created automatically.

  • One-command Helm install
  • Or download a CLI binary for Linux/macOS/Windows
  • Auto-creates ClusterRole, ServiceAccount, and CronJob
  • License key stored as a Kubernetes Secret
3

Inspector Scans Your Cluster

The Inspector runs inside your cluster: it validates RBAC permissions, scans for unused resources, builds a dependency graph, detects transitive orphans, and enriches every finding with cost estimates.

  • RBAC pre-check before every scan
  • Transitive orphan detection via dependency graph
  • Cost enrichment for GKE, EKS, AKS
  • Cluster health, efficiency & security scores
4

Results Appear in Dashboard

Findings are posted to your KorPro dashboard automatically. Your cluster appears under Settings → Inspector → Connected Clusters after the first scan (~1–2 min).

  • Auto-detects provider, region, and cluster name
  • Full orphan list with cost per resource
  • Direct vs. transitive orphan classification
  • Offline fallback to local JSON if API unreachable
5

Continuous Monitoring

The CronJob runs every 6 hours by default. Scan history, trends, and health scores update automatically so you can track your cleanup progress over time.

  • Configurable schedule (default: every 6h)
  • Scan history with per-scan metrics and trends
  • Failed scans never overwrite previous valid data
  • Auto-update notifications when a new Inspector version is available

Architecture Overview

The KorPro Inspector runs inside your cluster — only findings leave your environment

Your Kubernetes Cluster

Inspector CronJob runs here

HTTPS POST

Findings only — encrypted

KorPro Dashboard

Results & Insights

Your credentials never leave your cluster

Ready to Get Started?

Deploy the Inspector into your cluster and start seeing unused resources in minutes.