ci: add tests for Kubernetes 1.37 - #9887
Conversation
✅ Deploy Preview for cerulean-figolla-1f9435 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: cd7bb9ad41
ℹ️ About Codex in GitHub
Codex has been enabled to automatically 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 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #9887 +/- ##
=======================================
Coverage 81.31% 81.32%
=======================================
Files 264 264
Lines 40967 40967
=======================================
+ Hits 33314 33317 +3
+ Misses 7652 7649 -3
Partials 1 1 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
d2b41fd to
5846db0
Compare
|
@beckcl can you rebase with main branch? |
* add K8s 1.37 conformance and e2e tests * drop K8s 1.33 conformance tests * update compatibility matrix Signed-off-by: Clemens Beck <mail@beckcl.dev>
ClusterTrustBundle graduated to GA in K8s 1.37. All 1.37 review environments now enable ClusterTrustBundle. Previously it was tested on K8s 1.33 which introduced ClusterTrustBundle as beta. Signed-off-by: Clemens Beck <mail@beckcl.dev>
5846db0 to
1ec44a3
Compare
|
/retest |
1 similar comment
|
/retest |
What this PR does / why we need it:
Shift the test matrix to cover K8s 1.37, the newest K8s release:
https://kubernetes.io/releases/1.37/
Which issue(s) this PR fixes:
None
PR Checklist
git commit -s). See DCO: Sign your work./api), the API was discussed and agreed before the implementation. The API change can be in a separate PR, or in the same PR, but the API must be agreed before implementation. N/A if this PR does not contain API changes.make generate gen-check,make lint, and the unit-test/coverage build pass. (Flaky e2e failures are not considered breakages, butgen-check,lint, and coverage MUST pass.)release-notes/current/<section>/<pr-number>-<slug>.md(seerelease-notes/current/README.mdfor sections and naming). N/A if this PR does not contain non-trivial changes.make gen-checkand committed the result if API/helm charts/modules changed.release-notes/current/breaking_changes/.