Assessment: no repo change — the condition is already resolved
KubePodNotReady (openbao) and its two companions (KubePdbNotEnoughHealthyPods,
KubeStatefulSetReplicasMismatch) are **no…
Assessment: no repo change — live host intervention required (and the critical alert has already self-resolved)
No edits were made. This is genuinely not fixable in the repo, and live…
Assessment: no repo change is appropriate
VeleroBackupStale for paperless-daily is a correct alert reporting a real
RPO gap, but the cause is a cluster/node-layer event during…
Assessment: no repo change — one kubernetes Service backend is a dead IP
No edits were made. The manifests the issue points at are correct. The cause is live cluster state: the…
Assessment: no repo change is appropriate
The alert was real, the root cause was already fixed in-repo before this issue was filed, and I confirmed the fix is live, complete, and durable.…
Assessment: no repo change appropriate
Issue #617 (KubeContainerWaiting, namespace home-assistant) describes an
incident that is already fixed and no longer firing. I verified…
Assessment: no repo change appropriate — already fixed, verified live
KubePodNotReady (music-assistant) fired because Cilium's eBPF datapath was
dropping VLAN-tagged frames on VLAN 30…
Assessment: no repo change is appropriate
KubePodNotReady in home-assistant fired for shelly-manager-8c5cf458b-mwqcm and
matter-server-cd9dc894b-j4cvz because both carry a macvlan…
Assessment: no repo change is appropriate (issue #608)
KubeAPIInstanceUnreachable for 10.2.40.168:6443 is a live cluster-state
problem in the kubernetes Endpoints object, not a…
Assessment — no repo change (issue #607, KubeletInstanceUnreachable on k8s-3)
No edits were made. The alert was a planned maintenance outage that has already resolved, and the repo-side…