Assessment: no repo change is appropriate
KubeDeploymentReplicasMismatch for ai/embed-cand-kalm12b is real and still
firing, but the object it fires on does not exist in this repository…
Assessment: no repo change is appropriate (issue #744)
The alert was real while it fired, but nothing in this repository is wrong, and the object that triggered it does not exist in the…
Assessment: no repo change is appropriate — this needs one live cluster command
KubeJobFailed{namespace="velero", job_name="restore-test-29804160"} is still
firing, but the defect that…
Assessment: no repo change appropriate — the alert is already resolved by a completed decommission
NetbirdVpsBackupStale is no longer firing, and the reason is not the SQLite
busy-timeo…
Assessment: no repo change is appropriate for #723
NodeDiskIOSaturation on k8s-3 / nvme1n1 was a real saturation event, but the
dominant writer is not in this repository, and every in-repo…
Assessment: no repo change is appropriate
NodeSystemSaturation on k8s-3 was caused by a manually-applied vmtest Job whose manifest does not exist in this repository, and **the alert…
Assessment: no repo change is appropriate (issue #719, KubeJobFailed / vmtest)
The alert is real and the triage issue's diagnosis holds up against live state — but **none of the code or…