Repository navigation
feat: Bump containerd and pause for kubernetes 1.36.5 - #5157
Conversation
Hello riadelhajjaji-scality,My role is to assist you with the merge of this Available options
Available commands
Status report is not available. |
Waiting for approvalThe following approvals are needed before I can proceed with the merge:
Peer approvals must include at least 1 approval from the following list: |
|
/changie Enhanced Bump containerd to 2.3.6 and pause to 3.10.2 |
Branches have divergedThis pull request's source branch To avoid any integration risks, please re-synchronize them using one of the
Note: If you choose to rebase, you may have to ask me to rebuild |
|
|
the claude comment is about backfill changie entries related to dev/134, those are safe to ignore |
ezekiel-alexrod
left a comment
There was a problem hiding this comment.
Sorry for back and forth, but adding releases links to the changelog message could be handy too
Bumped containerd from 2.2.5 to 2.3.6, and the pause image from 3.10.1 to 3.10.2. containerd 2.3 is the first LTS release of containerd (supported for at least two years), aligned on the Kubernetes release cycle. Main changes from 2.2.5 to 2.3.6: - CRI: user namespaces with host networking, sandbox API updates, background stats collector, checkpoint restore through CreateContainer disabled by default (2.3.4) - NRI: many new plugin capabilities (sysctl, rlimits, network devices, seccomp...) - EROFS images and snapshotter improvements - Runtime: seccomp default profile hardening (AF_ALG sockets blocked, 2.3.1), /proc/interrupts and CPU thermal throttle sysfs paths masked in containers (2.3.6), shim and OOM watcher fixes - Security: authentication headers stripped when fetching descriptor URLs (2.3.5) Breaking change upstream: commas are no longer allowed in NRI plugin names. Changes that could impact MetalK8s: - NRI: not used by MetalK8s - seccomp default profile hardening: our workloads run with the RuntimeDefault profile, none uses AF_ALG sockets - checkpoint restore disabled by default: not used by MetalK8s - plugin config migration now runs on load: our config already uses `version = 3` - sandbox image references are normalized: our pinned `sandbox` image is a fully qualified name The pause 3.10.2 image only updates the Windows image base, the Linux image is unchanged. Its digest is not pinned, as the tag is re-published several times. The containerd.io 2.3.6 RPM is available in the docker-ce repository for EL8 and EL9. Ref: MK8S-352
Auto-generated-by: changie-add-changelog
3ad065b to
854a7d5
Compare
|
|
/approve |
Branches have divergedThis pull request's source branch To avoid any integration risks, please re-synchronize them using one of the
Note: If you choose to rebase, you may have to ask me to rebuild The following options are set: approve |
|
✅ Changelog check passed. |
|
LGTM |
In the queueThe changeset has received all authorizations and has been added to the The changeset will be merged in:
The following branches will NOT be impacted:
There is no action required on your side. You will be notified here once IMPORTANT Please do not attempt to modify this pull request.
If you need this pull request to be removed from the queue, please contact a The following options are set: approve |
|
I have successfully merged the changeset of this pull request
The following branches have NOT changed:
Please check the status of the associated issue MK8S-352. Goodbye riadelhajjaji-scality. |
Component: build, containers
Context:
MetalK8s 136.0 ships containerd 2.2.5 and the pause image 3.10.1.
containerd 2.3 is the first containerd LTS release (supported for at
least two years, aligned on the Kubernetes release cycle), and brings
security hardening and bug fixes. The pause 3.10.2 image is the
version expected by Kubernetes 1.36.
Summary:
to 2.3.6,
the latest
containerd.ioRPM available in the docker-ce repositoryfor EL8 and EL9 (2.3.7 is not packaged yet)
only the Windows image base changes, the Linux image is unchanged.
Its digest is not pinned, as the tag is re-published several times
Upstream changes reviewed against our configuration:
not used by MetalK8s
workloads use the RuntimeDefault profile, none uses AF_ALG sockets
not used by MetalK8s
version = 3sandboximageis a fully qualified name
Acceptance criteria:
containerd --version)Closes: #MK8S-352