Repository navigation
test(ci): summarize nested kubelet failures with a closed set of signals - #8303
Conversation
When a nested Kind cluster fails in the Kubernetes-provider trial, the retained evidence showed that the nested kubelet failed but not why. Add a closed classifier for the nested kubelet journal: it keeps the newest bounded bytes and drops a line cut part-way, matches each signal only when all its phrases are on the same line, emits only labels from one allow-list, and reports empty input as unavailable. The trial prints it for the control-plane and worker nodes of a failed Vanilla cluster. A test checks every output line against the allow-list and that no journal text is published. Part of #8186 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
✅
|
Code coverage overviewLanguages: Go Go / code-coverage/go
View coverage of the 1 most impacted file.
ℹ️ Calculations represent line coverage. Results may change as calculations are updated. Updated |
User trial at
🤖 Generated with Claude Code |
@codex review |
Codex Review Summary: ✅ CompletedThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 930125268e
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
> 🤖 Generated by the Agentic Engineer Match the explicit unknown-driver error emitted by kubelet. Cover successful CRI driver discovery alone and beside an unrelated failure, plus the actual driver error.
User trial at
🤖 Generated with Claude Code |
@codex review |
|
Codex Review: Didn't find any major issues. Breezy! Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |

Why
When a nested Kind cluster fails to start in the Kubernetes-provider trial, the saved evidence shows that the nested kubelet failed but not why. An earlier attempt kept giving misleading labels, because it searched the whole journal for loose phrases.
What
Failed trials now print a short summary of the nested kubelet journal, using only labels from a fixed list. A label is given only when all of its phrases appear on the same journal line, and no journal text is ever published.
Fixes #8186
🤖 Generated with Claude Code