kubernetes
Add glibc version constraints to the kubelet package
https://github.com/kubernetes/kubernetes/pull/118996 (https://github.com/kubernetes/release/issues/3076) will land in Kubernetes 1.29, containing a switch to debian:bookworm. This means we now require glibc 2.36 (compared to 2.31 on bullseye) for non static binaries like the kubelet.
The package of the kubelet could contain a constraint like this to highlight possible incompatibilities:
Requires: glibc >= 2.36
This needs to be done per release branch, while only affecting 1.29. We could also add a similar constraint to previous release branches (with 2.31).
cc @kubernetes/release-managers
We might upgrade the active branches to 1.21 as well so if that happens we need that constrain in the others as well
We'll bump back to bullseye with https://github.com/kubernetes/release/pull/3249, means we can add the 2.31 glibc constraint to all maintained release branches.
Current Ubuntu LTS (22.04) uses 2.35 (and the next version won't release until 5 months after Kubernetes 1.29). Am I understanding things correctly that Kubernetes 1.29 won't be usable on Ubuntu 22.04 LTS?
Current Ubuntu LTS (22.04) uses 2.35 (and the next version won't release until 5 months after Kubernetes 1.29). Am I understanding things correctly that Kubernetes 1.29 won't be usable on Ubuntu 22.04 LTS?
No, we still support the previous glibc version from bullseye per https://github.com/kubernetes/kubernetes/blob/master/build/build-image/cross/VERSION
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/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas 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
/remove-lifecycle stale
We meet the problem in https://github.com/kubernetes/release/pull/3430. Current workaround is to keep docker in 24.0 while docker v25.0 was released recently.
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/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas 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
/remove-lifecycle stale /retitle Add glibc version constraints to the kubelet package
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/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas 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