-
Notifications
You must be signed in to change notification settings - Fork 54
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
versions: add k8s 1.31, remove k8s 1.28 #3396
base: main
Are you sure you want to change the base?
Conversation
✅ Deploy Preview for constellation-docs ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
c1e09be
to
0dd6325
Compare
0dd6325
to
be2cd21
Compare
Yeah, I missed that. |
Does that even work? I created #3397 so that we can test 1.30 -> 1.31. |
0df582f
to
c70bdc4
Compare
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.
checked my files
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.
owned files lgtm
eb20368
to
eb60fdc
Compare
Co-Authored-By: Leonard Cohnen <[email protected]>
b1e967b
to
d5860bf
Compare
Coverage report
|
Unfortunately, d5860bf does not work: if a node from the worker scaling group manages to join the cluster, it will be paired with an existing worker nonetheless. |
Context
Kubernetes v1.31.0 was released on 2024-08-13.
Proposed change(s)
kubeadm.k8s.io/v1beta4
for cluster config - it's supported since v1.28 and v1.31 defaults to using it.registry.k8s.io
, because they are not published todocker.io
anymore.dl.k8s.io
because they are not published tostorage.googleapis.com
anymore.Additional info
Checklist