Repository navigation
Conversation
…g-reason scenarios
…eep cron schedules on time in fixtures
…alancer without nodes to the digest
… lose their network
…that holds node addresses
…top blaming DNS servers when config is unreadable
…d skip fix attempts on storage roots
…runtime class scenario its RuntimeClass
… a removed label or a gone node
…onger serves an image
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 this PR does
Adds about 300 blind, labelled failure scenarios to the alert-quality corpus, then teaches the engine to name the right root cause for them. Each scenario was written from a real Kubernetes failure without reading engine code. The label comes from Kubernetes behaviour, never from kwatch's output.
Where the scenarios come from
Every candidate was checked against the existing scenarios for duplicates, and rounds 6–7 were scored for how common, impactful, distinct and visible each failure is. Sources are Apache-2.0 / CC BY 4.0 or used as ideas only. No text was copied.
Engine rules added so far
Progress by area
Failing scenarios: 94 at the last count, down from about 160.
Fixture fixes (unrealistic data, not label changes)
Label changes (Kubernetes reason)
Round 1 label changes are listed in the first section of the earlier description (nodeSelector/anti-affinity root at the scheduling constraint, HPA without CPU request to the digest, NoExecute taint with ready replicas stays quiet, NotReady nodes page). Later label changes were made by review before the scenarios were pushed:
unknown.New user-facing wording (designer review pending for the newer lines)
Before merge
make verify, and ratchet.txt and SCORECARD.md regenerated.