chore(ci): collect K8s diagnostics on E2E test failure#25114
Merged
Conversation
f046f8f to
548d1d9
Compare
thomasqueirozb
approved these changes
Apr 2, 2026
8d09d33 to
601665d
Compare
9 tasks
Add a diagnostic step to the K8s E2E workflow that runs on failure. Captures pod logs, events, configs, and node resource usage to avoid deep manual investigation when tests fail. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
0aefbe2 to
f72ce22
Compare
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Summary
Add a diagnostic step to the K8s E2E workflow that runs on failure (
if: failure()). This captures:vector-*namespace: pod descriptions, events, configmaps--all-containers=trueMotivated by #25111 where the root cause (a config field rejected by Vector on startup) would have been immediately visible from pod logs.
How did you test this PR?
Validated YAML syntax. The step uses
if: failure()so it only runs when tests fail. Zero overhead on green runs.Change Type
Is this a breaking change?
Does this PR include user facing changes?
no-changeloglabel to this PR.References
🤖 Generated with Claude Code