Kubernetes Health Diagnostics

Kubernetes Health Diagnostics

Dynamic, discovery-driven health checks for any Kubernetes cluster configuration

BEFORE YOU START

Known Issues Prevented

Quick Start

1. Verify cluster access: Ensure kubectl is configured and can reach your cluster
2. Run discovery: Execute discover_apis.py to detect installed operators
3. Dispatch agents: Use the orchestrator to run health checks based on discovery

# Step 1: Verify kubectl context
kubectl config current-context
kubectl cluster-info

# Step 2: Run API discovery
uv run .claude/​skills/​kubernetes-health/​scripts/​discover_apis.py

# Step 3: Review detected operators and dispatch health agents

Critical Rules

Always

• Verify kubectl context before running health checks
• Use read-only kubectl commands (get, describe, logs)
• Run core health checks before operator-specific checks
• Aggregate results using the provided scoring methodology

Never

• Modify cluster resources during health checks
• Expose secret values in health reports (metadata only)
• Skip context verification for production clusters
• Assume operator presence without API discovery

Common Mistakes

Bundled Resources

Scripts

References

Templates

Dependencies

Required

Optional

Supported Operators

The skill automatically detects and dispatches specialized agents for:

Health Scoring

Troubleshooting

kubectl connection issues

# Verify context
kubectl config current-context

# Test connectivity
kubectl cluster-info

# Check permissions
kubectl auth can-i get pods --all-namespaces

Discovery returns empty results

• Ensure cluster is reachable
• Check RBAC permissions for API discovery
• Verify kubectl version compatibility

Agent dispatch failures

• Confirm discovered API group matches agent trigger
• Check agent file exists in .claude/​agents/​specialized/​kubernetes/
• Review agent tool restrictions

Setup Checklist

• kubectl configured and connected to cluster
• Python 3.11+ installed
• uv installed for script execution
• Read permissions on cluster resources
• Agent files present in .claude/​agents/​specialized/​kubernetes/