-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Bump kubernetes-client-bom from 6.11.0 to 6.12.1 #40045
Conversation
This comment has been minimized.
This comment has been minimized.
c3c34f8
to
9db94c5
Compare
This comment has been minimized.
This comment has been minimized.
Ping @metacosm :) |
Looks OK for us. Thank you! |
Signed-off-by: Marc Nuri <[email protected]>
Signed-off-by: Marc Nuri <[email protected]>
9db94c5
to
5af1b8f
Compare
Should it be backported to 3.10/3.8? |
Status for workflow
|
There shouldn't be any breaking changes in this new release. I guess backporting is safe, but @metacosm should be the one providing advice here. |
I'm going to check but let's reverse the question: is there any advantage to upgrading in terms of functionality / fixes / etc.? |
The most important fix has to do with OpenID Connect and access to EKS clusters. Other than that, there isn't much more (for runtime mode). |
Kubernetes Client 6.12.0 was just released: https://github.com/fabric8io/kubernetes-client/releases/tag/v6.12.0
Kubernetes Client 6.12.1 was just released: https://github.com/fabric8io/kubernetes-client/releases/tag/v6.12.1
/cc @metacosm