Dependency update - Golang 1.22.3/1.21.10
cpanato opened this issue · 2 comments
Tracking info
Link to any previous tracking issue: #3529
Golang mailing list announcement: https://groups.google.com/g/golang-announce/c/eoj5XPifNtA/m/WJAi2b2WBQAJ
SIG Release Slack thread: https://kubernetes.slack.com/archives/CJH2GBF7Y/p1714660078790139
Work items
-
kube-cross
,go-runner
,releng-ci
image updates: #3604-
kube-cross
image promotion: kubernetes/k8s.io#6792
-
go-runner
image promotion: kubernetes/k8s.io#6791
-
releng-ci
image promotion: kubernetes/k8s.io#6793
-
After go-runner image promotion
-
distroless-iptables
image update: #3605- image promotion: kubernetes/k8s.io#6794
After kube-cross and distroless-iptables image promotions
-
kubernetes/kubernetes update (
master
): kubernetes/kubernetes#124828Ensure the following have been updated within the PR:
-
.go-version
file - kube-cross image
- go-runner image
- distroless-iptables image
- publishing bot rules
- test image
-
Note
This update may require an update to go.sum files, for example: kubernetes/kubernetes#118507
This will require an API Review approval.
After kubernetes/kubernetes (master) has been updated
-
k8s-cloud-builder
andk8s-ci-builder
image updates: #3613
-
kubekins
/krte
image variants update: kubernetes/test-infra#32605
Cherry picks
- Kubernetes 1.30: kubernetes/kubernetes#124829
- Kubernetes 1.29: kubernetes/kubernetes#124830
- Kubernetes 1.28: kubernetes/kubernetes#124831
- Kubernetes 1.27: kubernetes/kubernetes#124832
- publishing bot rule updates for active Golang versions: kubernetes/kubernetes#124888
After kubernetes/kubernetes (release branches) has been updated
-
k8s-cloud-builder
andk8s-ci-builder
image updates: #3618
-
kubekins
/krte
image updates: kubernetes/test-infra#32621
Follow-up items
- Ensure the Golang issue template is updated with any new requirements
/assign
cc: @kubernetes/release-engineering
work is done
/close
@cpanato: Closing this issue.
In response to this:
work is done
/close
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-sigs/prow repository.