<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Cgroups on CuraDevOps</title><link>https://curadevops.metacog.co.kr/tags/cgroups/</link><description>Recent content in Cgroups on CuraDevOps</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 07 Oct 2026 17:37:04 +0000</lastBuildDate><atom:link href="https://curadevops.metacog.co.kr/tags/cgroups/index.xml" rel="self" type="application/rss+xml"/><item><title>Kubernetes cgroup v1 Deprecated: Nodes Blocked from Starting in K8s 1.35+</title><link>https://curadevops.metacog.co.kr/insights/2026-10-07-the-shift-to-cgroup-v2-in-kubernetes-what-you-need-to-know/</link><pubDate>Wed, 07 Oct 2026 17:37:04 +0000</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-10-07-the-shift-to-cgroup-v2-in-kubernetes-what-you-need-to-know/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Plan:&lt;/strong> Kubernetes 1.35 (currently GA, EOL 2027-02-28) defaults failCgroupV1 to true, meaning kubelet refuses to start on cgroup v1 nodes without an explicit override. Audit all Linux nodes for cgroup version and complete migration to cgroup v2 before upgrading any cluster to 1.35 or later.&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> Kubernetes 1.31 is past EOL (2025-11-11, 330d ago) · Kubernetes 1.25 is past EOL (2023-10-27, 1076d ago) · Kubernetes 1.35 EOL 2027-02-28 · deprecation mentioned (no explicit date found)&lt;/li>
&lt;/ul></description></item></channel></rss>