kindplane diagnostics¶

Run diagnostics on cluster components.
Usage¶
Flags¶
| Flag | Short | Description |
|---|---|---|
--component | Component to diagnose (crossplane, providers, eso, helm) | |
--namespace | -n | Namespace to inspect |
--release | Helm release name (for helm component) | |
--max-logs | Maximum log lines per container (default: 30) | |
--timeout | Timeout for collection (default: 30s) |
Description¶
The diagnostics command collects and displays diagnostic information for cluster components to help troubleshoot issues.
It gathers detailed information about:
- Pod status and conditions
- Container states and restarts
- Recent container logs
- Provider health status
- Helm release status
Components¶
| Component | Description |
|---|---|
crossplane | Crossplane controller and RBAC manager |
providers | Crossplane provider pods and status |
eso | External Secrets Operator (if installed) |
helm | Specific Helm release |
Examples¶
Diagnose All Components¶
Diagnose Crossplane¶
Diagnose Providers¶
Diagnose Specific Helm Release¶
Increase Log Output¶
Output¶
Healthy Components¶
Cluster Diagnostics
--------------------------------------------------
Running diagnostics for cluster 'kindplane-dev'...
✓ No issues found for component: crossplane
✓ No issues found for component: providers
╭────────────────────────────────────────────────╮
│ All Healthy │
│ All components are functioning correctly. │
╰────────────────────────────────────────────────╯
Issues Found¶
Cluster Diagnostics
--------------------------------------------------
Running diagnostics for cluster 'kindplane-dev'...
╭────────────────────────────────────────────────────────────────╮
│ Provider Diagnostics │
│ │
│ ✗ provider-aws │
│ Package: xpkg.upbound.io/upbound/provider-aws:v1.1.0 │
│ Conditions: │
│ ✗ Healthy: False │
│ Reason: UnhealthyPackageRevision │
│ Message: cannot resolve package dependencies... │
│ │
│ Pod Status │
│ provider-aws-7b8f9d6c5-xk2jl (crossplane-system) │
│ Phase: Running │
│ Ready: 0/1 containers │
│ Restarts: 3 │
│ │
│ Recent Logs: │
│ error: failed to initialize provider │
│ error: cannot connect to registry │
╰────────────────────────────────────────────────────────────────╯
When to Use¶
After Bootstrap Failures¶
When kindplane up fails, diagnostics are shown automatically. For additional investigation:
Debugging Provider Issues¶
Helm Chart Issues¶
# Diagnose a specific Helm release
kindplane diagnostics --component helm --release my-app --namespace default
Ongoing Monitoring¶
Tips¶
Combine with Logs¶
For ongoing issues, combine diagnostics with log streaming:
# Get snapshot of issues
kindplane diagnostics --component providers
# Then stream live logs
kindplane logs --component providers --follow
CI/CD Integration¶
Capture diagnostics on failure: