-
Notifications
You must be signed in to change notification settings - Fork 506
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
Switch to debian 12 (bookworm) #3128
Comments
Notification mail is out https://groups.google.com/g/kubernetes-sig-release/c/M-7rt-jvE-8/m/zK0lLxu6AgAJ Setting lazy consens to July 1st before moving on with this topic. |
Consensus reached, moving forward with debian-base. |
Mostly done, let's keep this open until we have a |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
This is done |
@saschagrunert Do we have an issue to track updating k8s-cloud-builder/k8s-ci-bulider to Debian 12 (bookworm)? |
No, the idea was to stay on bullseye as long as possible for compatibility reasons. Like having a policy to always use the lowest available glibc version when building Kubernetes. We may wanna add documentation about this, though. |
I think that would be very helpful so we can reference it in cases such as #3430 |
Add a note to the golang update issue template about using the oldest available Debian release for glibc compatibility of the kubelet. Refers to: kubernetes#3128 (comment) Signed-off-by: Sascha Grunert <[email protected]>
Closing the loop: #3437 |
Tracking issue to switch to debian 12 for our base images:
post-release-push-image-debian-base
in k/release:https://console.cloud.google.com/cloud-build/builds/29add73b-b9c7-457f-8708-bbc0fdcf63a2
post-release-push-image-debian-iptables
:https://console.cloud.google.com/cloud-build/builds/2ddfb03f-2ff1-4e07-8080-71be492709ed?project=960211007710
see use new distroless kube-proxy image kubernetes#111060)
post-release-push-image-setcap
in k/release:https://prow.k8s.io/view/gs/kubernetes-jenkins/logs/post-release-push-image-setcap/1678773957659987968
post-release-push-image-kube-cross
in k/release:https://prow.k8s.io/view/gs/kubernetes-jenkins/logs/post-release-push-image-kube-cross/1679757580605329408
post-release-push-image-releng-ci
in k/release:https://prow.k8s.io/view/gs/kubernetes-jenkins/logs/post-release-push-image-releng-ci/1679046245521297408
post-release-push-image-k8s-ci-builder
in k/release:https://prow.k8s.io/view/gs/kubernetes-jenkins/logs/post-release-push-image-k8s-ci-builder/1681720502244085760
post-release-push-image-go-runner
in k/release:https://prow.k8s.io/view/gs/kubernetes-jenkins/logs/post-release-push-image-go-runner/1696484688291434496
distroless-iptables: provide debian 12 bookworm variant #3235
Update distroless version to v0.3.0 #3236
distroless-iptables: fix
grep
command #3237Update distroless-iptables image version to v0.3.1 #3240
post-release-push-image-distroless-iptables
in k/release:https://prow.k8s.io/view/gs/kubernetes-jenkins/logs/post-release-push-image-distroless-iptables/1696855492782985216
https://prow.k8s.io/view/gs/kubernetes-jenkins/logs/post-release-push-image-distroless-iptables/1696891736472686592
The text was updated successfully, but these errors were encountered: