klarity scan --env prod
╔══════════════════════════════════════════════════════════════════════╗
║ klarity scan — 2026-03-21 14:32:07 CST ║
║ Environments: 3 | Clusters: 7 scanned | Issues: 5 found ║
╚══════════════════════════════════════════════════════════════════════╝
━━━ 🔴 PROD ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
── prod-us-east-1 ──────────────────────────────────────────────────
💀 OOMKilled (2 pods)
┌────────────┬─────────────────┬──────────┬────────┬──────────┬─────────┐
│ Namespace │ Pod │ Requests │ Limits │ NS Quota │ Restarts│
├────────────┼─────────────────┼──────────┼────────┼──────────┼─────────┤
│ ml-serving │ model-inf-8x2-a │ 512Mi │ 1Gi │ 8Gi/10Gi │ 14 │
└────────────┴─────────────────┴──────────┴────────┴──────────┴─────────┘
🔥 CrashLoopBackOff — Application Errors (2 pods)
┌──────────────┬────────────────┬──────────┬──────────────────────────────────────┐
│ Namespace │ Pod │ Restarts │ Root Cause (from logs) │
├──────────────┼────────────────┼──────────┼──────────────────────────────────────┤
│ checkout │ cart-svc-3d1-r │ 47 │ FATAL: password auth failed "cartdb" │
│ notifications│ email-wrk-1a-m │ 12 │ ConnectionRefused: rabbitmq:5672 │
└──────────────┴────────────────┴──────────┴──────────────────────────────────────┘
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Summary: 4 issues in prod | 1 in staging | 0 in dev
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━Strictly Read-Only
Only `get`, `list`, and log tail operations. klarity never mutates resources, making it perfectly safe to run against production clusters by design.
Multi-Cluster Native
Reads your kubeconfig and uses Go routines to scan across contexts in parallel. Environments (prod, dev, staging) are auto-detected instantly.
Root-Cause Extraction
No more digging through 30-line stack traces. klarity parses Java, Python, and Go logs to extract the exact one-line error causing a CrashLoopBackOff.
Configure once. Run forever.
Run klarity init to launch the TUI onboarding wizard. It auto-detects your environments and outputs a clean, human-editable YAML config. Adding a new cluster is as simple as adding two lines.
# ~/.klarityconfig.yaml
version: 1
environments:
- name: prod
tier: critical
clusters:
- context: prod-us-east-1
- context: prod-eu-west-1