chore(test): Update Kubernetes versions in workflows to 1.31 and 1.33. Fixes #11937
Description of your changes:
Fixes #11937
Updates the Kind cluster Kubernetes versions in all GitHub workflows from [v1.29.2, v1.30.2, v1.31.0] to [v1.30.13, v1.33.1] to use the lowest and highest supported versions as requested in issue #11937.
Updated workflows:
- .github/workflows/periodic.yml
- .github/workflows/kfp-webhooks.yml
- .github/workflows/e2e-test.yml
- .github/workflows/upgrade-test.yml
- .github/workflows/kfp-kubernetes-execution-tests.yml
- .github/workflows/kfp-samples.yml
- .github/workflows/sdk-execution.yml
Checklist:
- [x] You have signed off your commits
- [x] The title for your pull request (PR) should follow our title convention. Learn more about the pull request title convention used in this repository.
Testing
- [x] Verified that both kindest/node:v1.30.13 and kindest/node:v1.33.1 images are available in Kind v0.29.0 release (https://github.com/kubernetes-sigs/kind/releases)
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: Once this PR has been reviewed and has the lgtm label, please assign dharmitd for approval. For more information see the Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
Hi @johnwroge. Thanks for your PR.
I'm waiting for a kubeflow member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
🚫 This command cannot be processed. Only organization members or owners can use the commands.
@johnwroge could you please rebase?
/cc @mprahl
@mprahl not sure you are aware, but KFP needs to support at least the same versions as the KF platform. For KF 1.10 it was from 1.29 to 1.31.
You can confirm the supported versions for the next KF releases with @varodrig, in case you haven't done yet.
/ok-to-test
@varodrig
@hbelmiro , I wasn't aware of that but I was just going off of the Kubernetes versions that will be supported at KFP 2.6 release time: https://kubernetes.io/releases/
@varodrig @hbelmiro Thank you for pointing this out! I can update the versions and complete the rebase as soon as someone confirms the correct range.
@varodrig
@hbelmiro , I wasn't aware of that but I was just going off of the Kubernetes versions that will be supported at KFP 2.6 release time: https://kubernetes.io/releases/
It makes total sense @mprahl. @varodrig it sounds like we should do the same for the entire platform for 1.11.