Repository navigation
Conversation
…g-reason scenarios
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What was missed
make alert-qualityfailed on 13 of the 29 new gap scenarios (wrong root, no incident, or fallback to the workload), plus gate-level misses: three notify first messages over 5m (pod-stuck-terminating-finalizer 11m15s, release-image-pull-deadline 7m15s, cron-active-deadline-exceeded 6m), and a 6-message incident in the staging day.Engine changes per miss
volume-bound-elsewhereroots at the PV. The misleading provisioner sentence is dropped for it.wrong-type). Right-typed secrets keep blaming the registry.used-missingrow also covers ReplicaFailure/FailedCreate effects.node-no-execute-taint-tolerated.DeploymentPausedEditfinding (paused 30m with a recorded template edit, digest tier); the edit is not blamed as a release. Negative twindeployment-paused-no-editstays quiet.Network.Conflict("already exists for an interface", "address already in use"...) roots at the node from one stuck pod.Label / fixture changes (Kubernetes reason)
scheduling//<constraint>, as in fit-host-port-taken and unschedulable-taint; the message already names the Deployment fix.customresourcedefinition//...(kwatch's id for the built-in kind); added the empty EndpointSlice the controller always keeps.unknown; nothing in cluster state (no node condition, event or policy) names n3, so naming it would be a guess. Fixture gets the Service ClusterIP the callers dial.New user-facing wording (designer review)
Scorecard
Before (902af29): 25/30 gates; correct root 96.8%; wrong root at likely+ 5; first message wrong root 5; must-not-blame 3; over budget 1; notify first message max 11m15s.
After: 30/30 gates; correct root 99.1%; wrong high-confidence 0/289; wrong stated 0; must-not-blame 0; over budget 0; notify first message max 4m15s. ratchet.txt and SCORECARD.md regenerated;
make verifypasses.Runtime behaviour beyond the engine is unchanged, so no
e2elabel.Designer wording applied
Conversion: "Requests for its resources that need version conversion fail."; paused: "Deployment has been paused for N with a pod template edit that has not rolled out." plus a resume step (
kubectl rollout resume deploy/X -n NS); CNI: "an IP address or route it assigns is already in use"; unknown cause: only when the lead's own error is a network timeout to an address and the node, registry and services were checked, the message now reads "No cause found in cluster state: ... Its error is a network timeout to ADDR, so check the path to that address." The generic unknown wording is unchanged. Goldens changed by this: crd-conversion-webhook-gone, deployment-paused-with-pending-edit, network-packet-loss-to-node, node-cni-ip-conflict.