<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Patch-Release on CuraDevOps</title><link>https://curadevops.metacog.co.kr/tags/patch-release/</link><description>Recent content in Patch-Release on CuraDevOps</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 17 Aug 2026 12:38:40 +0000</lastBuildDate><atom:link href="https://curadevops.metacog.co.kr/tags/patch-release/index.xml" rel="self" type="application/rss+xml"/><item><title>containerd 2.3.4 released with breaking checkpoint-restore change</title><link>https://curadevops.metacog.co.kr/insights/2026-08-17-containerd-2-3-4/</link><pubDate>Mon, 17 Aug 2026 12:38:40 +0000</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-08-17-containerd-2-3-4/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Plan:&lt;/strong> Despite being a patch release, 2.3.4 ships a breaking change: checkpoint restore in CreateContainer is now disabled by default, requiring an explicit config opt-in. Also fixes a memory leak in the OOM watcher and binary protobuf shim corruption. Review workloads using CRIU/checkpoint restore before upgrading; schedule the upgrade this quarter.&lt;/li>
&lt;li>&lt;strong>CI/CD — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Signals:&lt;/strong> containerd 2.3 EOL 2028-04-30 · deprecation mentioned (no explicit date found)&lt;/li>
&lt;/ul></description></item><item><title>Docker Engine 29.7.2 fixes image pull regressions from 29.7.0</title><link>https://curadevops.metacog.co.kr/insights/2026-08-10-v29-7-2/</link><pubDate>Mon, 10 Aug 2026 13:02:04 +0000</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-08-10-v29-7-2/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Plan:&lt;/strong> Two regressions introduced in 29.7.0 — image pulls rejecting hardlink targets and file-permission failures on older kernels — are fixed in 29.7.2; if you upgraded to 29.7.x recently, schedule a patch to 29.7.2 to restore stable image pull behavior.&lt;/li>
&lt;li>&lt;strong>CI/CD — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;/ul></description></item><item><title>etcd v3.5.33 patch release flags breaking change</title><link>https://curadevops.metacog.co.kr/insights/2026-07-27-v3-5-33/</link><pubDate>Mon, 27 Jul 2026 14:28:32 +0000</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-07-27-v3-5-33/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Plan:&lt;/strong> etcd backs every Kubernetes control plane, and a breaking-change flag on a patch release is unusual — review the CHANGELOG and upgrade guide before rolling this out to clusters; no hard deadline, but unreviewed breaking changes in a core datastore warrant a planned change window rather than routine rollout.&lt;/li>
&lt;li>&lt;strong>CI/CD — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Signals:&lt;/strong> breaking-change flagged&lt;/li>
&lt;/ul></description></item></channel></rss>