-
Notifications
You must be signed in to change notification settings - Fork 444
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
Upgrade Kubernetes to v1.30.7 #2463
base: master
Are you sure you want to change the base?
Changes from all commits
f81a1a2
b608ee0
bc49242
dc3625c
0a83183
538cec6
11e577e
ed01b40
b915471
146148c
5c48e4b
532ab00
8c2a15c
f3088b2
a63e300
aa9c300
000729d
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -33,6 +33,6 @@ jobs: | |
strategy: | ||
fail-fast: false | ||
matrix: | ||
kubernetes-version: ["v1.27.11", "v1.28.7", "v1.29.2"] | ||
kubernetes-version: ["v1.28.7", "v1.29.2", "v1.30.7"] | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. We can also add one that tests whatever is the cutting edge version so we can get notified of any incompatibility earlier There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. SGTM. The newest version of k8s is 1.32.0 now. WDYT👀 @kubeflow/wg-automl-leads |
||
# Comma Delimited | ||
experiments: ["darts-cpu"] |
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.
Do you want to migrate to k8s 1.31 in the followup PR ?
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.
Yeah, I'd like to. But I'm busy this week. If it's not urgent, I'll raise another PR to migrate to k8s 1.31 next week.
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.
I think that step by step upgrading would be better so that we can easily pick the commit when we find the issue on the specific K8s version.
So, I would recommend upgrading 1 K8s version in 1 PR.