2.7 KiB
2.7 KiB
| 1 | label | meaning | diagnose_commands | jeannie_fix_commands | other_fix_commands | risk | auto_fix | notes |
|---|---|---|---|---|---|---|---|---|
| 2 | Inventory | The canonical homelab inventory is missing or invalid, so Jeannie may use stale or unsafe defaults. | ./jeannie inventory-check;./jeannie validate | none | Edit homelab.yml | medium | no | Fix the inventory before running mutating pipeline commands. |
| 3 | Documentation freshness | Generated docs are stale or README.md.tmpl contains an unsupported template variable. | ./jeannie validate | none | scripts/render-docs | low | candidate | A docs-render Jeannie command could safely wrap scripts/render-docs later. |
| 4 | Backup readiness | Gitea, OpenTofu state, or restore drill backups are missing or stale. | ./jeannie backup-status;./jeannie recover-plan | ./jeannie backup-gitea;./jeannie state-backup;./jeannie drill-restore | none | medium | no | Backups are usually safe to create, but restore drills and retention choices should stay explicit. |
| 5 | GitOps health | Argo CD applications, repository wiring, or sync health need attention. | ./jeannie gitops-status;./jeannie status | ./jeannie apps | none | medium | no | App syncs can change workloads, so Jeannie should explain before applying. |
| 6 | DNS and RPi health | Pi-hole, Unbound, Uptime Kuma, RPi SSH, or RPi Docker state is unhealthy. | ./jeannie doctor-rpi;./jeannie status | ./jeannie rpi-services | none | medium | no | RPi service redeploys can restart DNS, so require explicit user action. |
| 7 | Cluster health | Kubernetes API, nodes, pods, or Pimox workers are unhealthy. | ./jeannie doctor-cluster;./jeannie status;./jeannie workers list | ./jeannie start-cluster;./jeannie control-plane taint | none | medium | no | Start/taint operations are safe when intentional, but not automatic. |
| 8 | Edge health | OCI edge, Traefik, public routes, or Gitea public routing need attention. | ./jeannie doctor-edge;./jeannie cert-check;./jeannie status | ./jeannie plan edge;./jeannie up | none | high | no | Edge fixes can alter public routing or apply infrastructure. |
| 9 | Capacity pressure | Resource requests, limits, node pressure, storage pressure, or placement signals need attention. | ./jeannie resource-budget;./jeannie capacity;./jeannie control-plane status | ./jeannie control-plane taint;./jeannie workers list | none | medium | no | Most capacity fixes require manifest changes or scheduling decisions. |
| 10 | Security posture | Tailscale ACL policy or static security checks need attention. | ./jeannie tailnet-policy-check;./jeannie security-scan | none | Edit infra/tailscale/tailnet-policy.hujson | medium | no | Policy changes should be reviewed before applying to the tailnet. |
| 11 | Public certificates | Public DNS, TLS expiry, website/Gitea URLs, or DuckDNS edge drift need attention. | ./jeannie cert-check;./jeannie doctor-edge | ./jeannie plan edge;./jeannie up | none | medium | no | Certificate and edge fixes can affect public access. |