-
Notifications
You must be signed in to change notification settings - Fork 240
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
Update dockerfiles to use go v1.22 #2931
Conversation
1.23 is out, any reason not going all the way up? |
we should probably wait for at least 1.23.1 in case they snuck any bugs in the .0, but this is a good idea. some nice new features in 1.23. @aggarwal0009 8 files does not seem like enough compared to when we moved to 1.21 |
Updated |
/azp run Azure Container Networking PR |
Azure Pipelines successfully started running 1 pipeline(s). |
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'll update the PR check requirements once this tests clean so it can be queued to merge
/azp run Azure Container Networking PR |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run Azure Container Networking PR |
Azure Pipelines successfully started running 1 pipeline(s). |
#2930 depends on this (adding it to link the PRs) |
/azp run Azure Container Networking PR |
Azure Pipelines successfully started running 1 pipeline(s). |
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.
Since this is modifying NPM, please run both NPM Azure Pipelines tests and merge once green. They are not “required checks” because GitHub does not support requiring checks that trigger conditionally (i.e. only when npm/ directory is modified)
/azp run NPM Conformance Tests
/azp run NPM Scale Test
/azp run NPM Conformance Tests |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run NPM Scale Test |
Azure Pipelines successfully started running 1 pipeline(s). |
Reason for Change:
Upgrading dockerfiles to go v1.22 to support device plugin which introduces kubelet dependencies requiring go 1.22
Reference to device plugin PR: #2886
Issue Fixed:
Requirements:
Notes: