-
Notifications
You must be signed in to change notification settings - Fork 591
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: seperate latest k8s release tests #1621
Conversation
In another upcoming change we're switching testing of older kubernetes releases onto GKE (from KIND) so that they're running against conformant production quality cluster configurations. This patch moves the tests which must remain in kind (for now) into their own job as a blocker for releases.
Codecov Report
@@ Coverage Diff @@
## next #1621 +/- ##
==========================================
- Coverage 62.39% 62.30% -0.10%
==========================================
Files 82 82
Lines 7202 7202
==========================================
- Hits 4494 4487 -7
- Misses 2381 2386 +5
- Partials 327 329 +2
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No issues with the split proposed here itself; I do have other questions I'll raise elsewhere.
What this PR does / why we need it:
In another upcoming change we're switching testing
of older kubernetes releases onto GKE (from KIND)
so that they're running against conformant production
quality cluster configurations. This patch moves
the tests which must remain in kind (for now) into
their own job as a blocker for releases.
Which issue this PR fixes
Resolves #1616