Run operator E2E on one Kubernetes version per PR - #6540
Merged
Conversation
Every pull request update runs the operator E2E suite against three kind node versions, about 20 large-runner minutes per run, while cross-version compatibility almost never breaks within a single PR. Run only the newest version on pull_request events. Pushes to main and manual dispatches keep the full matrix, so a version-specific regression still surfaces on main within one CI cycle. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #6540 +/- ##
==========================================
+ Coverage 78.69% 78.70% +0.01%
==========================================
Files 777 777
Lines 76797 76797
==========================================
+ Hits 60434 60442 +8
+ Misses 16358 16350 -8
Partials 5 5 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
Member
Author
|
/retest |
1 similar comment
Member
Author
|
/retest |
JAORMX
approved these changes
Sep 8, 2026
aponcedeleonch
approved these changes
Sep 8, 2026
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
3 participants
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
Every pull request update runs the operator E2E suite against three kind node versions. That is about 20 large-runner minutes per PR Checks run, roughly a fifth of the suite's cost, and cross-version compatibility almost never breaks within a single PR.
Run only the newest version (1.35) on
pull_requestevents. Pushes to main and manual dispatches keep the full three-version matrix, so a version-specific regression still surfaces on main within one CI cycle rather than never.Expected saving: about 13 large-runner minutes per PR run, roughly $330 per month at current PR volume.
Type of change
Test plan
actionlinton the changed workflow with the repo's custom runner labels declared: clean.kindest/nodestill matches every occurrence, including the one inside thefromJSONstring, so both lists are bumped together.E2E Tests Operator (kindest/node:v1.35.1)job.Does this introduce a user-facing change?
No.
Special notes for reviewers
github.event_nameinside a reusable workflow is the caller's event, sopull_requesthere means PR Checks andpushmeans Main build. The matrix expression is the smallest way to make the list conditional without a separate matrix-preparation job.Generated with Claude Code
🤖 Generated with Claude Code