Skip to content
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

Closed
44 tasks done
saschagrunert opened this issue Jun 21, 2023 · 10 comments
Closed
44 tasks done

Switch to debian 12 (bookworm) #3128

saschagrunert opened this issue Jun 21, 2023 · 10 comments
Assignees
Labels
kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.

Comments

@saschagrunert
Copy link
Member

saschagrunert commented Jun 21, 2023

Tracking issue to switch to debian 12 for our base images:

@k8s-ci-robot k8s-ci-robot added needs-kind Indicates a PR lacks a `kind/foo` label and requires one. needs-priority labels Jun 21, 2023
@saschagrunert saschagrunert added priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. and removed needs-kind Indicates a PR lacks a `kind/foo` label and requires one. needs-priority labels Jun 22, 2023
@saschagrunert
Copy link
Member Author

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.

@saschagrunert
Copy link
Member Author

Consensus reached, moving forward with debian-base.

@saschagrunert
Copy link
Member Author

Mostly done, let's keep this open until we have a gcr.io/distroless/static-debian12

@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 27, 2024
@xmudrii
Copy link
Member

xmudrii commented Jan 28, 2024

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 28, 2024
@saschagrunert
Copy link
Member Author

This is done

@xmudrii
Copy link
Member

xmudrii commented Jan 29, 2024

@saschagrunert Do we have an issue to track updating k8s-cloud-builder/k8s-ci-bulider to Debian 12 (bookworm)?

@saschagrunert
Copy link
Member Author

saschagrunert commented Jan 29, 2024

@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.

@xmudrii
Copy link
Member

xmudrii commented Jan 29, 2024

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

saschagrunert added a commit to saschagrunert/release that referenced this issue Jan 29, 2024
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 <sgrunert@redhat.com>
@saschagrunert
Copy link
Member Author

Closing the loop: #3437

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Projects
None yet
Development

No branches or pull requests

4 participants