{"id":39118,"date":"2026-05-03T13:37:11","date_gmt":"2026-05-03T11:37:11","guid":{"rendered":"https:\/\/www.cloudmagazin.com\/2026\/05\/03\/kubernetes-1-36-migration-enterprise-checkliste-cgroup-v2\/"},"modified":"2026-06-22T13:34:58","modified_gmt":"2026-06-22T11:34:58","slug":"kubernetes-1-36-migration-enterprise-checkliste-cgroup-v2","status":"publish","type":"post","link":"https:\/\/www.cloudmagazin.com\/en\/2026\/05\/03\/kubernetes-1-36-migration-enterprise-checkliste-cgroup-v2\/","title":{"rendered":"Kubernetes 1.36 Migration: Cluster Checklist for Enterprise Teams"},"content":{"rendered":"<p style=\"color:#6190a9;font-size:0.9em;margin:0 0 16px;\">8 min read<\/p>\n<p><strong>Kubernetes 1.36 was released on April 22, 2026. The two main changes are the final removal of cgroup-v1 support and the general availability of Dynamic Resource Allocation (DRA). For Enterprise Ops teams, this means concrete tasks within the next 60 days before upstream support and security patches for older cluster versions expire. A migration checklist without theoretical overhead.<\/strong><\/p>\n<h2>Key Takeaways<\/h2>\n<ul>\n<li>Kubernetes 1.36 GA on 04\/22\/2026: cgroup-v1 support removed, DRA now generally available<\/li>\n<li>Those still running on cgroup-v1 (indicated by <span style=\"font-family:monospace;background:#f4f4f4;padding:1px 5px;border-radius:3px;font-size:0.92em;\">&#8211;cgroup-driver=cgroupfs<\/span>) must migrate to containerd + cgroup-v2 before upgrading<\/li>\n<li>DRA GA: Resource provider installation and NodeFeature CRDs are now mandatory for GPU\/FPGA workloads<\/li>\n<li>Minimum containerd version for 1.36 support: 1.7.x, 2.0 recommended<\/li>\n<li>Timeframe: Kubernetes 1.33 end-of-life in October 2026 &#8211; those still on 1.33 must upgrade now<\/li>\n<\/ul>\n<p style=\"font-size:0.88em;color:#666;margin:20px 0 32px 0;border-top:1px solid #e5e5e5;border-bottom:1px solid #e5e5e5;padding:10px 0;\"><span style=\"color:#202528;font-weight:700;text-transform:uppercase;font-size:0.72em;letter-spacing:0.14em;margin-right:14px;\">Related<\/span><a href=\"https:\/\/www.cloudmagazin.com\/en\/2026\/05\/03\/lenovo-thinkedge-se60n-gen-2-im-praxischeck-wann-edge\/\" style=\"color:#333;text-decoration:underline;\">Edge Computing 2026: ThinkEdge SE60n Gen 2 in Praxischeck<\/a>&nbsp;&nbsp;<span style=\"color:#ccc;\">\/<\/span>&nbsp;&nbsp;FinOps 2026: Enterprise Cloud Costs in Focus<\/p>\n<h2>What is Kubernetes 1.36 and why is this release migration-critical?<\/h2>\n<p><strong>What is Kubernetes 1.36?<\/strong> Kubernetes 1.36 is the release of the open-source container orchestration system published on April 22, 2026, marking the final removal of cgroup-v1 support and the general availability of Dynamic Resource Allocation (DRA) for hardware resources like GPUs and FPGAs.<\/p>\n<p>Kubernetes 1.36 is the first release to completely remove cgroup-v1 support. cgroup v1 (Control Groups version 1) was the classic Linux kernel interface for resource isolation &#8211; RAM limits, CPU quotas, process hierarchies. Since Kubernetes 1.25, cgroup-v2 has been the standard path. With 1.36, cgroup-v1 is no longer deprecated but completely removed.<\/p>\n<p>This means: Any node still running with the cgroupfs driver under cgroup-v1 will not start after an upgrade to 1.36. The Kubelet throws an error during initialization checks. This is not a soft transition &#8211; it is a hard stop.<\/p>\n<div style=\"background:#f5f9fc;border-radius:8px;padding:24px 28px;margin:28px 0;\">\n<p style=\"margin:0 0 12px 0;font-size:0.8em;font-weight:700;text-transform:uppercase;letter-spacing:0.15em;color:#0b5394;\">Migration Statistics<\/p>\n<div style=\"display:flex;flex-wrap:wrap;gap:20px;\">\n<div style=\"flex:1;min-width:150px;text-align:center;\">\n<p style=\"font-size:2em;font-weight:800;color:#0b5394;margin:0;\">23%<\/p>\n<p style=\"color:#666;font-size:0.82em;margin:4px 0 0 0;\">According to the CNCF survey Q1 2026, 23% of enterprise clusters were still running on cgroup-v1 or had an unclear status<\/p>\n<\/div>\n<div style=\"flex:1;min-width:150px;text-align:center;\">\n<p style=\"font-size:2em;font-weight:800;color:#0b5394;margin:0;\">Oct 2026<\/p>\n<p style=\"color:#666;font-size:0.82em;margin:4px 0 0 0;\">K8s 1.33 end-of-life &#8211; those still on 1.33 have 5 months<\/p>\n<\/div>\n<div style=\"flex:1;min-width:150px;text-align:center;\">\n<p style=\"font-size:2em;font-weight:800;color:#0b5394;margin:0;\">containerd 2.0<\/p>\n<p style=\"color:#666;font-size:0.82em;margin:4px 0 0 0;\">Recommended version for K8s 1.36 &#8211; 1.7.x is minimum, 2.0 is the supported path<\/p>\n<\/div>\n<\/div>\n<\/div>\n<p><strong>Related: <a href=\"https:\/\/www.cloudmagazin.com\/en\/2026\/05\/03\/state-of-finops-2026-technology-value-management-dach-cloud\/\">State of FinOps 2026: Why FinOps is now called Technology Value Management and what it means for DACH cloud budgets<\/a><\/strong><\/p>\n<h2>Step 1: Verify Cluster Status (cgroup Version and containerd)<\/h2>\n<p>Before anyone upgrades, each node needs an inventory check. Two checks, both of which can be performed remotely via kubectl:<\/p>\n<p><strong>cgroup Version per Node:<\/strong><\/p>\n<div style=\"background:#1a1a2e;color:#e8e8e8;border-radius:6px;padding:16px 20px;margin:16px 0;font-family:monospace;font-size:0.88em;overflow-x:auto;\">\nkubectl get nodes -o custom-columns=&#8221;NAME:.metadata.name&#8221; | \\<br \/>\n&nbsp;&nbsp;xargs -I{} kubectl describe node {} | grep &#8220;Container Runtime&#8221;\n<\/div>\n<p>Or directly on the node:<br \/>\nstat -fc %T \/sys\/fs\/cgroup<br \/>\nOutput &#8220;tmpfs&#8221; = cgroup-v1, &#8220;cgroup2fs&#8221; = cgroup-v2<\/p>\n<p><strong>containerd Version and Configuration:<\/strong><\/p>\n<div style=\"background:#1a1a2e;color:#e8e8e8;border-radius:6px;padding:16px 20px;margin:16px 0;font-family:monospace;font-size:0.88em;overflow-x:auto;\">\ncontainerd &#8211;version<br \/>\nMin: 1.7.x | Recommended: 2.0.x\n<\/div>\n<p>Check containerd-cgroup-driver:<br \/>\ngrep -i cgroup \/etc\/containerd\/config.toml<br \/>\nShould show &#8220;SystemdCgroup = true&#8221; (cgroup-v2)<\/p>\n<p>If you see <span style=\"font-family:monospace;background:#f4f4f4;padding:1px 5px;border-radius:3px;font-size:0.92em;\">SystemdCgroup = false<\/span> or no entry, you are still in cgroupfs mode. This is the main blocker for the 1.36 upgrade.<\/p>\n<h2>Step 2: cgroup-v2 Migration at Node Level<\/h2>\n<p>Migrating nodes from cgroup-v1 to cgroup-v2 requires a kernel parameter change and a node drain-restart cycle. No rolling upgrade is possible &#8211; each node must be drained.<\/p>\n<p><strong>1. Adjust Kernel Boot Parameters<\/strong> (GRUB or systemd-boot depending on OS):<\/p>\n<div style=\"background:#1a1a2e;color:#e8e8e8;border-radius:6px;padding:16px 20px;margin:16px 0;font-family:monospace;font-size:0.88em;overflow-x:auto;\">\n\/etc\/default\/grub &#8211; Disable cgroup-v1:<br \/>\nGRUB_CMDLINE_LINUX=&#8221;systemd.unified_cgroup_hierarchy=1 cgroup_no_v1=all&#8221;<br \/>\nupdate-grub &amp;&amp; reboot\n<\/div>\n<p><strong>2. Update containerd Configuration:<\/strong><\/p>\n<div style=\"background:#1a1a2e;color:#e8e8e8;border-radius:6px;padding:16px 20px;margin:16px 0;font-family:monospace;font-size:0.88em;overflow-x:auto;\">\n\/etc\/containerd\/config.toml<br \/>\n[plugins.&#8221;io.containerd.grpc.v1.cri&#8221;.containerd.runtimes.runc.options]<br \/>\nSystemdCgroup = true\n<\/div>\n<p><strong>3. Adjust Kubelet Configuration:<\/strong><\/p>\n<div style=\"background:#1a1a2e;color:#e8e8e8;border-radius:6px;padding:16px 20px;margin:16px 0;font-family:monospace;font-size:0.88em;overflow-x:auto;\">\nkubelet-config.yaml<br \/>\ncgroupDriver: systemd\n<\/div>\n<p>Restart sequence:<br \/>\nkubectl drain &lt;node&gt; &#8211;ignore-daemonsets<br \/>\nsystemctl restart containerd kubelet<br \/>\nkubectl uncordon &lt;node&gt;\n<\/p>\n<figure style=\"margin:36px 0;padding:0;\">\n<blockquote style=\"position:relative;margin:0;padding:30px 34px 28px;background:linear-gradient(135deg,#013a47 0%,#004a59 100%);border-radius:12px;box-shadow:0 10px 30px rgba(0,40,60,0.18);overflow:hidden;\"><p>\n<span aria-hidden=\"true\" style=\"position:absolute;right:22px;top:6px;font-family:Georgia,serif;font-size:90px;line-height:1;color:#0bb7fd;opacity:0.18;\">&rdquo;<\/span><\/p>\n<div style=\"font-family:'SF Mono','Monaco','Consolas',monospace;font-size:10.5px;color:#0bb7fd;letter-spacing:0.18em;text-transform:uppercase;margin-bottom:13px;\">\/\/ Quote<\/div>\n<p style=\"margin:0;font-size:1.15em;line-height:1.6;color:#f2fafd;font-weight:500;position:relative;\">A node that doesn&#8217;t cleanly reboot after the drain &#8211; that&#8217;s when the planning meets reality. Plan for 45 minutes per node, not 15.<\/p>\n<footer style=\"margin-top:16px;font-size:0.92em;color:rgba(255,255,255,0.72);font-style:normal;\"><strong style=\"color:#fff;\">Alec Chizhik<\/strong> &middot; cloudmagazin<\/footer>\n<\/blockquote>\n<\/figure>\n<h2>Step 3: Set Up DRA &#8211; Dynamic Resource Allocation<\/h2>\n<p>DRA is generally available in 1.36. What does this mean for teams with GPU or FPGA workloads? DRA replaces the old device plugin mechanism for hardware resources. If you are using NVIDIA GPUs via the NVIDIA device plugin, check if the vendor driver is already DRA-compatible.<\/p>\n<p>DRA mandatory checks for GPU environments:<\/p>\n<div style=\"background:#1a1a2e;color:#e8e8e8;border-radius:6px;padding:16px 20px;margin:16px 0;font-family:monospace;font-size:0.88em;overflow-x:auto;\">\nCheck if DRA feature gate is active:<br \/>\nkubectl get &#8211;raw \/api\/v1 | grep -i &#8220;dynamic&#8221;\n<\/div>\n<p>Verify ResourceSlice and DeviceClass CRDs:<br \/>\nkubectl get crd | grep resource.k8s.io<br \/>\nExpected output:<br \/>\ndeviceclasses.resource.k8s.io<br \/>\nresourceclaims.resource.k8s.io<br \/>\nresourceslices.resource.k8s.io\n<\/p>\n<p>NVIDIA introduced DRA support with NVIDIA GPU Operator 25.x. AMD ROCm DRA support is scheduled for Q2 2026. For Intel GPUs (Gaudi, Arc), separate verification is required &#8211; Intel Extensions for Kubernetes have their own release cycle.<\/p>\n<h2>Pros and Cons: Direct to 1.36 vs. Intermediate Step via 1.35<\/h2>\n<div style=\"display:grid;grid-template-columns:1fr 1fr;gap:20px;margin:20px 0;\">\n<div style=\"background:#f0fff4;border-radius:8px;padding:20px;\">\n<p style=\"font-weight:800;color:#27ae60;text-transform:uppercase;font-size:0.8em;letter-spacing:0.1em;margin:0 0 12px 0;\">Direct to 1.36<\/p>\n<ul style=\"margin:0;padding-left:18px;line-height:1.7;color:#333;font-size:0.92em;\">\n<li style=\"margin-bottom:6px;\">One migration instead of two (no intermediate version)<\/li>\n<li style=\"margin-bottom:6px;\">Immediate DRA-GA usage<\/li>\n<li style=\"margin-bottom:6px;\">Longer support horizon (EOL for 1.36: ~April 2027)<\/li>\n<li style=\"margin-bottom:6px;\">Single downtime window instead of two<\/li>\n<\/ul>\n<\/div>\n<div style=\"background:#fff5f5;border-radius:8px;padding:20px;\">\n<p style=\"font-weight:800;color:#e74c3c;text-transform:uppercase;font-size:0.8em;letter-spacing:0.1em;margin:0 0 12px 0;\">Intermediate Step via 1.35<\/p>\n<ul style=\"margin:0;padding-left:18px;line-height:1.7;color:#333;font-size:0.92em;\">\n<li style=\"margin-bottom:6px;\">Prepare cgroup-v2 migration in 1.35 without 1.36 changes<\/li>\n<li style=\"margin-bottom:6px;\">DRA still in beta in 1.35 \u2013 fewer surprises if no GPU workload<\/li>\n<li style=\"margin-bottom:6px;\">Risk splitting: Infrastructure migration and API upgrade separately<\/li>\n<\/ul>\n<\/div>\n<\/div>\n<h2>Frequently Asked Questions<\/h2>\n<details style=\"margin-bottom:12px;\">\n<summary><strong>Do I need to enable cgroup-v2 before upgrading to K8s 1.36?<\/strong><\/summary>\n<p>Yes, this is a strict requirement. K8s 1.36 will not start on nodes still running in cgroup-v1 mode. The migration must be completed at the node level before the Kubernetes upgrade (GRUB parameters + containerd configuration + Kubelet config).<\/p>\n<\/details>\n<details style=\"margin-bottom:12px;\">\n<summary><strong>Which containerd version do I need for Kubernetes 1.36?<\/strong><\/summary>\n<p>The minimum required version is containerd 1.7.x. For full support, containerd 2.0.x is recommended. containerd 1.6.x is no longer compatible. Verify with <span style=\"font-family:monospace;background:#f4f4f4;padding:1px 5px;border-radius:3px;font-size:0.92em;\">containerd &#8211;version<\/span>.<\/p>\n<\/details>\n<details style=\"margin-bottom:12px;\">\n<summary><strong>Is DRA a replacement for the NVIDIA Device Plugin?<\/strong><\/summary>\n<p>Mid-term yes, short-term both can run in parallel. DRA is available in K8s 1.36 GA, but vendor drivers have their own roadmaps. NVIDIA GPU Operator supports DRA starting with version 25.x. The Device Plugin will continue to run in parallel until vendors officially switch to DRA-only.<\/p>\n<\/details>\n<details style=\"margin-bottom:12px;\">\n<summary><strong>What happens to my existing resource quotas after the cgroup-v2 migration?<\/strong><\/summary>\n<p>Memory limits and CPU limits remain semantically identical under cgroup-v2. The key difference: cgroup-v2 enforces limits more strictly, especially in memory overcommit scenarios. In rare cases, workloads that were at the limits under cgroup-v1 may receive OOM signals earlier under cgroup-v2.<\/p>\n<\/details>\n<details style=\"margin-bottom:12px;\">\n<summary><strong>How do I check if my managed Kubernetes service (EKS, GKE, AKS) is already on cgroup-v2?<\/strong><\/summary>\n<p>EKS: Amazon Linux 2023 defaults to cgroup-v2. Amazon Linux 2 is still on cgroup-v1. GKE: All nodes with Container-Optimized OS since 2023 are on cgroup-v2. AKS: Standard Ubuntu nodes are on cgroup-v2 starting with AKS 1.25. Verify on a node with <span style=\"font-family:monospace;background:#f4f4f4;padding:1px 5px;border-radius:3px;font-size:0.92em;\">stat -fc %T \/sys\/fs\/cgroup<\/span>.<\/p>\n<\/details>\n<div style=\"background:#f5f9fc;border-radius:8px;padding:22px 26px;margin:32px 0;\">\n<p style=\"font-weight:700;font-size:0.83em;text-transform:uppercase;letter-spacing:0.12em;color:#202528;margin:0 0 12px 0;\">Network<\/p>\n<p style=\"margin:0;line-height:1.7;font-size:0.92em;\"><a href=\"https:\/\/www.digital-chiefs.de\/industrie-5-0-als-fuehrungsentscheidung-was-cios-aus-der-hannover-messe-2026-mitnehmen\/\" style=\"color:#333;text-decoration:underline;\">Industry 5.0: What CIOs Need to Decide Now<\/a> &nbsp;(Digital Chiefs)&nbsp;&nbsp;|&nbsp;&nbsp;<a href=\"https:\/\/mybusinessfuture.com\/nearshoring-2026-wann-sich-der-wechsel-lohnt-und-wann-nicht\/\" style=\"color:#333;text-decoration:underline;\">Nearshoring 2026: Decision Framework<\/a> &nbsp;(MyBusinessFuture)<\/p>\n<\/div>\n<p style=\"color:#888;font-size:0.85em;text-align:right;font-style:italic;\">Source Image: Pexels \/ cottonbro studio (px:6804597)<\/p>\n","protected":false},"excerpt":{"rendered":"Kubernetes 1.36 removes cgroup v1 support and brings DRA to General Availability.","protected":false},"author":31,"featured_media":39112,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"_yoast_wpseo_meta-robots-noindex":"","_yoast_wpseo_meta-robots-nofollow":"","_yoast_wpseo_meta-robots-adv":"","_yoast_wpseo_canonical":"","_yoast_wpseo_opengraph-title":"","_yoast_wpseo_opengraph-description":"","_yoast_wpseo_opengraph-image":"https:\/\/www.cloudmagazin.com\/wp-content\/uploads\/2026\/05\/kubernetes-1-36-migration-enterprise-checkliste-cgroup-v2-dra-cover-hero.jpg","_yoast_wpseo_opengraph-image-id":0,"_yoast_wpseo_twitter-title":"","_yoast_wpseo_twitter-description":"","_yoast_wpseo_twitter-image":"https:\/\/www.cloudmagazin.com\/wp-content\/uploads\/2026\/05\/kubernetes-1-36-migration-enterprise-checkliste-cgroup-v2-dra-cover-hero.jpg","_yoast_wpseo_twitter-image-id":0,"pre_headline":"","bildquelle":"","teasertext":"","language":"de","_evm_translation_lang":"","featured_post":0,"featured_post_sortierung":0,"_wp_old_slug":[],"footnotes":""},"categories":[929],"tags":[],"industry":[],"class_list":["post-39118","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-cm-guides"],"evm_reading_time_minutes":6,"wpml_language":"en","wpml_translation_of":39108,"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v27.9 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>Kubernetes 1.36 Migration: The Cluster Checklist for Enterprise Teams After cgro<\/title>\n<meta name=\"description\" content=\"Kubernetes 1.36 Migration Guide: cgroup-v1 removed, DRA GA. Step-by-step checklist for enterprise teams - from status check to full cluster upgrade.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.cloudmagazin.com\/en\/2026\/05\/03\/kubernetes-1-36-migration-enterprise-checkliste-cgroup-v2\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Kubernetes 1.36 Migration: The Cluster Checklist for Enterprise Teams After cgro\" \/>\n<meta property=\"og:description\" content=\"Kubernetes 1.36 Migration Guide: cgroup-v1 removed, DRA GA. Step-by-step checklist for enterprise teams - from status check to full cluster upgrade.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.cloudmagazin.com\/en\/2026\/05\/03\/kubernetes-1-36-migration-enterprise-checkliste-cgroup-v2\/\" \/>\n<meta property=\"og:site_name\" content=\"cloudmagazin\" \/>\n<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/cloudmagazincom\/\" \/>\n<meta property=\"article:published_time\" content=\"2026-05-03T11:37:11+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-06-22T11:34:58+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.cloudmagazin.com\/wp-content\/uploads\/2026\/05\/kubernetes-1-36-migration-enterprise-checkliste-cgroup-v2-dra-cover-hero.jpg\" \/>\n<meta name=\"author\" content=\"Alec Chizhik\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:image\" content=\"https:\/\/www.cloudmagazin.com\/wp-content\/uploads\/2026\/05\/kubernetes-1-36-migration-enterprise-checkliste-cgroup-v2-dra-cover-hero.jpg\" \/>\n<meta name=\"twitter:creator\" content=\"@cloudmagazin\" \/>\n<meta name=\"twitter:site\" content=\"@cloudmagazin\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Alec Chizhik\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"5 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"NewsArticle\",\"@id\":\"https:\\\/\\\/www.cloudmagazin.com\\\/en\\\/2026\\\/05\\\/03\\\/kubernetes-1-36-migration-enterprise-checkliste-cgroup-v2\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.cloudmagazin.com\\\/en\\\/2026\\\/05\\\/03\\\/kubernetes-1-36-migration-enterprise-checkliste-cgroup-v2\\\/\"},\"author\":{\"name\":\"Alec Chizhik\",\"@id\":\"https:\\\/\\\/www.cloudmagazin.com\\\/en\\\/#\\\/schema\\\/person\\\/ce38baaa19a580268aedce096597eb3c\"},\"headline\":\"Kubernetes 1.36 Migration: Cluster Checklist for Enterprise Teams\",\"datePublished\":\"2026-05-03T11:37:11+00:00\",\"dateModified\":\"2026-06-22T11:34:58+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.cloudmagazin.com\\\/en\\\/2026\\\/05\\\/03\\\/kubernetes-1-36-migration-enterprise-checkliste-cgroup-v2\\\/\"},\"wordCount\":1066,\"publisher\":{\"@id\":\"https:\\\/\\\/www.cloudmagazin.com\\\/en\\\/#organization\"},\"image\":{\"@id\":\"https:\\\/\\\/www.cloudmagazin.com\\\/en\\\/2026\\\/05\\\/03\\\/kubernetes-1-36-migration-enterprise-checkliste-cgroup-v2\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.cloudmagazin.com\\\/wp-content\\\/uploads\\\/2026\\\/05\\\/kubernetes-1-36-migration-enterprise-checkliste-cgroup-v2-dra-cover-hero.jpg\",\"articleSection\":[\"Guides\"],\"inLanguage\":\"en-US\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.cloudmagazin.com\\\/en\\\/2026\\\/05\\\/03\\\/kubernetes-1-36-migration-enterprise-checkliste-cgroup-v2\\\/\",\"url\":\"https:\\\/\\\/www.cloudmagazin.com\\\/en\\\/2026\\\/05\\\/03\\\/kubernetes-1-36-migration-enterprise-checkliste-cgroup-v2\\\/\",\"name\":\"Kubernetes 1.36 Migration: The Cluster Checklist for Enterprise Teams After cgro\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.cloudmagazin.com\\\/en\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/www.cloudmagazin.com\\\/en\\\/2026\\\/05\\\/03\\\/kubernetes-1-36-migration-enterprise-checkliste-cgroup-v2\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/www.cloudmagazin.com\\\/en\\\/2026\\\/05\\\/03\\\/kubernetes-1-36-migration-enterprise-checkliste-cgroup-v2\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.cloudmagazin.com\\\/wp-content\\\/uploads\\\/2026\\\/05\\\/kubernetes-1-36-migration-enterprise-checkliste-cgroup-v2-dra-cover-hero.jpg\",\"datePublished\":\"2026-05-03T11:37:11+00:00\",\"dateModified\":\"2026-06-22T11:34:58+00:00\",\"description\":\"Kubernetes 1.36 Migration Guide: cgroup-v1 removed, DRA GA. Step-by-step checklist for enterprise teams - from status check to full cluster upgrade.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.cloudmagazin.com\\\/en\\\/2026\\\/05\\\/03\\\/kubernetes-1-36-migration-enterprise-checkliste-cgroup-v2\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.cloudmagazin.com\\\/en\\\/2026\\\/05\\\/03\\\/kubernetes-1-36-migration-enterprise-checkliste-cgroup-v2\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.cloudmagazin.com\\\/en\\\/2026\\\/05\\\/03\\\/kubernetes-1-36-migration-enterprise-checkliste-cgroup-v2\\\/#primaryimage\",\"url\":\"https:\\\/\\\/www.cloudmagazin.com\\\/wp-content\\\/uploads\\\/2026\\\/05\\\/kubernetes-1-36-migration-enterprise-checkliste-cgroup-v2-dra-cover-hero.jpg\",\"contentUrl\":\"https:\\\/\\\/www.cloudmagazin.com\\\/wp-content\\\/uploads\\\/2026\\\/05\\\/kubernetes-1-36-migration-enterprise-checkliste-cgroup-v2-dra-cover-hero.jpg\",\"width\":1024,\"height\":576,\"caption\":\"B\u00fcroumgebung: Arbeiten im Kontext von Kubernetes-Migration. (Foto: c. s. (px:6804597) \\\/ Pexels)\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.cloudmagazin.com\\\/en\\\/2026\\\/05\\\/03\\\/kubernetes-1-36-migration-enterprise-checkliste-cgroup-v2\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/www.cloudmagazin.com\\\/en\\\/home\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Kubernetes 1.36 Migration: Cluster Checklist for Enterprise Teams\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.cloudmagazin.com\\\/en\\\/#website\",\"url\":\"https:\\\/\\\/www.cloudmagazin.com\\\/en\\\/\",\"name\":\"cloudmagazin\",\"description\":\"Inspiration f\u00fcr Businessentscheider\",\"publisher\":{\"@id\":\"https:\\\/\\\/www.cloudmagazin.com\\\/en\\\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.cloudmagazin.com\\\/en\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/www.cloudmagazin.com\\\/en\\\/#organization\",\"name\":\"cloudmagazin\",\"url\":\"https:\\\/\\\/www.cloudmagazin.com\\\/en\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.cloudmagazin.com\\\/en\\\/#\\\/schema\\\/logo\\\/image\\\/\",\"url\":\"https:\\\/\\\/www.cloudmagazin.com\\\/wp-content\\\/uploads\\\/2020\\\/04\\\/cloudmagazin-logo-klein_menu.jpg\",\"contentUrl\":\"https:\\\/\\\/www.cloudmagazin.com\\\/wp-content\\\/uploads\\\/2020\\\/04\\\/cloudmagazin-logo-klein_menu.jpg\",\"width\":150,\"height\":150,\"caption\":\"cloudmagazin\"},\"image\":{\"@id\":\"https:\\\/\\\/www.cloudmagazin.com\\\/en\\\/#\\\/schema\\\/logo\\\/image\\\/\"},\"sameAs\":[\"https:\\\/\\\/www.facebook.com\\\/cloudmagazincom\\\/\",\"https:\\\/\\\/x.com\\\/cloudmagazin\",\"https:\\\/\\\/www.linkedin.com\\\/showcase\\\/cloudmagazin\\\/\"]},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.cloudmagazin.com\\\/en\\\/#\\\/schema\\\/person\\\/ce38baaa19a580268aedce096597eb3c\",\"name\":\"Alec Chizhik\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.cloudmagazin.com\\\/wp-content\\\/uploads\\\/2026\\\/03\\\/alec-chizhik.jpg\",\"url\":\"https:\\\/\\\/www.cloudmagazin.com\\\/wp-content\\\/uploads\\\/2026\\\/03\\\/alec-chizhik.jpg\",\"contentUrl\":\"https:\\\/\\\/www.cloudmagazin.com\\\/wp-content\\\/uploads\\\/2026\\\/03\\\/alec-chizhik.jpg\",\"caption\":\"Alec Chizhik\"},\"description\":\"Alec is the Chief Digital Officer at Evernine and writes about cloud architectures, IT security, and digital operations practices.\",\"sameAs\":[\"https:\\\/\\\/www.linkedin.com\\\/in\\\/alecchizhik\\\/\"],\"url\":\"https:\\\/\\\/www.cloudmagazin.com\\\/en\\\/author\\\/alec\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Kubernetes 1.36 Migration: The Cluster Checklist for Enterprise Teams After cgro","description":"Kubernetes 1.36 Migration Guide: cgroup-v1 removed, DRA GA. Step-by-step checklist for enterprise teams - from status check to full cluster upgrade.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.cloudmagazin.com\/en\/2026\/05\/03\/kubernetes-1-36-migration-enterprise-checkliste-cgroup-v2\/","og_locale":"en_US","og_type":"article","og_title":"Kubernetes 1.36 Migration: The Cluster Checklist for Enterprise Teams After cgro","og_description":"Kubernetes 1.36 Migration Guide: cgroup-v1 removed, DRA GA. Step-by-step checklist for enterprise teams - from status check to full cluster upgrade.","og_url":"https:\/\/www.cloudmagazin.com\/en\/2026\/05\/03\/kubernetes-1-36-migration-enterprise-checkliste-cgroup-v2\/","og_site_name":"cloudmagazin","article_publisher":"https:\/\/www.facebook.com\/cloudmagazincom\/","article_published_time":"2026-05-03T11:37:11+00:00","article_modified_time":"2026-06-22T11:34:58+00:00","og_image":[{"url":"https:\/\/www.cloudmagazin.com\/wp-content\/uploads\/2026\/05\/kubernetes-1-36-migration-enterprise-checkliste-cgroup-v2-dra-cover-hero.jpg","type":"","width":"","height":""}],"author":"Alec Chizhik","twitter_card":"summary_large_image","twitter_image":"https:\/\/www.cloudmagazin.com\/wp-content\/uploads\/2026\/05\/kubernetes-1-36-migration-enterprise-checkliste-cgroup-v2-dra-cover-hero.jpg","twitter_creator":"@cloudmagazin","twitter_site":"@cloudmagazin","twitter_misc":{"Written by":"Alec Chizhik","Est. reading time":"5 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"NewsArticle","@id":"https:\/\/www.cloudmagazin.com\/en\/2026\/05\/03\/kubernetes-1-36-migration-enterprise-checkliste-cgroup-v2\/#article","isPartOf":{"@id":"https:\/\/www.cloudmagazin.com\/en\/2026\/05\/03\/kubernetes-1-36-migration-enterprise-checkliste-cgroup-v2\/"},"author":{"name":"Alec Chizhik","@id":"https:\/\/www.cloudmagazin.com\/en\/#\/schema\/person\/ce38baaa19a580268aedce096597eb3c"},"headline":"Kubernetes 1.36 Migration: Cluster Checklist for Enterprise Teams","datePublished":"2026-05-03T11:37:11+00:00","dateModified":"2026-06-22T11:34:58+00:00","mainEntityOfPage":{"@id":"https:\/\/www.cloudmagazin.com\/en\/2026\/05\/03\/kubernetes-1-36-migration-enterprise-checkliste-cgroup-v2\/"},"wordCount":1066,"publisher":{"@id":"https:\/\/www.cloudmagazin.com\/en\/#organization"},"image":{"@id":"https:\/\/www.cloudmagazin.com\/en\/2026\/05\/03\/kubernetes-1-36-migration-enterprise-checkliste-cgroup-v2\/#primaryimage"},"thumbnailUrl":"https:\/\/www.cloudmagazin.com\/wp-content\/uploads\/2026\/05\/kubernetes-1-36-migration-enterprise-checkliste-cgroup-v2-dra-cover-hero.jpg","articleSection":["Guides"],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/www.cloudmagazin.com\/en\/2026\/05\/03\/kubernetes-1-36-migration-enterprise-checkliste-cgroup-v2\/","url":"https:\/\/www.cloudmagazin.com\/en\/2026\/05\/03\/kubernetes-1-36-migration-enterprise-checkliste-cgroup-v2\/","name":"Kubernetes 1.36 Migration: The Cluster Checklist for Enterprise Teams After cgro","isPartOf":{"@id":"https:\/\/www.cloudmagazin.com\/en\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.cloudmagazin.com\/en\/2026\/05\/03\/kubernetes-1-36-migration-enterprise-checkliste-cgroup-v2\/#primaryimage"},"image":{"@id":"https:\/\/www.cloudmagazin.com\/en\/2026\/05\/03\/kubernetes-1-36-migration-enterprise-checkliste-cgroup-v2\/#primaryimage"},"thumbnailUrl":"https:\/\/www.cloudmagazin.com\/wp-content\/uploads\/2026\/05\/kubernetes-1-36-migration-enterprise-checkliste-cgroup-v2-dra-cover-hero.jpg","datePublished":"2026-05-03T11:37:11+00:00","dateModified":"2026-06-22T11:34:58+00:00","description":"Kubernetes 1.36 Migration Guide: cgroup-v1 removed, DRA GA. Step-by-step checklist for enterprise teams - from status check to full cluster upgrade.","breadcrumb":{"@id":"https:\/\/www.cloudmagazin.com\/en\/2026\/05\/03\/kubernetes-1-36-migration-enterprise-checkliste-cgroup-v2\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.cloudmagazin.com\/en\/2026\/05\/03\/kubernetes-1-36-migration-enterprise-checkliste-cgroup-v2\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.cloudmagazin.com\/en\/2026\/05\/03\/kubernetes-1-36-migration-enterprise-checkliste-cgroup-v2\/#primaryimage","url":"https:\/\/www.cloudmagazin.com\/wp-content\/uploads\/2026\/05\/kubernetes-1-36-migration-enterprise-checkliste-cgroup-v2-dra-cover-hero.jpg","contentUrl":"https:\/\/www.cloudmagazin.com\/wp-content\/uploads\/2026\/05\/kubernetes-1-36-migration-enterprise-checkliste-cgroup-v2-dra-cover-hero.jpg","width":1024,"height":576,"caption":"B\u00fcroumgebung: Arbeiten im Kontext von Kubernetes-Migration. (Foto: c. s. (px:6804597) \/ Pexels)"},{"@type":"BreadcrumbList","@id":"https:\/\/www.cloudmagazin.com\/en\/2026\/05\/03\/kubernetes-1-36-migration-enterprise-checkliste-cgroup-v2\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.cloudmagazin.com\/en\/home\/"},{"@type":"ListItem","position":2,"name":"Kubernetes 1.36 Migration: Cluster Checklist for Enterprise Teams"}]},{"@type":"WebSite","@id":"https:\/\/www.cloudmagazin.com\/en\/#website","url":"https:\/\/www.cloudmagazin.com\/en\/","name":"cloudmagazin","description":"Inspiration f\u00fcr Businessentscheider","publisher":{"@id":"https:\/\/www.cloudmagazin.com\/en\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.cloudmagazin.com\/en\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/www.cloudmagazin.com\/en\/#organization","name":"cloudmagazin","url":"https:\/\/www.cloudmagazin.com\/en\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.cloudmagazin.com\/en\/#\/schema\/logo\/image\/","url":"https:\/\/www.cloudmagazin.com\/wp-content\/uploads\/2020\/04\/cloudmagazin-logo-klein_menu.jpg","contentUrl":"https:\/\/www.cloudmagazin.com\/wp-content\/uploads\/2020\/04\/cloudmagazin-logo-klein_menu.jpg","width":150,"height":150,"caption":"cloudmagazin"},"image":{"@id":"https:\/\/www.cloudmagazin.com\/en\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/www.facebook.com\/cloudmagazincom\/","https:\/\/x.com\/cloudmagazin","https:\/\/www.linkedin.com\/showcase\/cloudmagazin\/"]},{"@type":"Person","@id":"https:\/\/www.cloudmagazin.com\/en\/#\/schema\/person\/ce38baaa19a580268aedce096597eb3c","name":"Alec Chizhik","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.cloudmagazin.com\/wp-content\/uploads\/2026\/03\/alec-chizhik.jpg","url":"https:\/\/www.cloudmagazin.com\/wp-content\/uploads\/2026\/03\/alec-chizhik.jpg","contentUrl":"https:\/\/www.cloudmagazin.com\/wp-content\/uploads\/2026\/03\/alec-chizhik.jpg","caption":"Alec Chizhik"},"description":"Alec is the Chief Digital Officer at Evernine and writes about cloud architectures, IT security, and digital operations practices.","sameAs":["https:\/\/www.linkedin.com\/in\/alecchizhik\/"],"url":"https:\/\/www.cloudmagazin.com\/en\/author\/alec\/"}]}},"_links":{"self":[{"href":"https:\/\/www.cloudmagazin.com\/en\/wp-json\/wp\/v2\/posts\/39118","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.cloudmagazin.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.cloudmagazin.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.cloudmagazin.com\/en\/wp-json\/wp\/v2\/users\/31"}],"replies":[{"embeddable":true,"href":"https:\/\/www.cloudmagazin.com\/en\/wp-json\/wp\/v2\/comments?post=39118"}],"version-history":[{"count":4,"href":"https:\/\/www.cloudmagazin.com\/en\/wp-json\/wp\/v2\/posts\/39118\/revisions"}],"predecessor-version":[{"id":47323,"href":"https:\/\/www.cloudmagazin.com\/en\/wp-json\/wp\/v2\/posts\/39118\/revisions\/47323"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.cloudmagazin.com\/en\/wp-json\/wp\/v2\/media\/39112"}],"wp:attachment":[{"href":"https:\/\/www.cloudmagazin.com\/en\/wp-json\/wp\/v2\/media?parent=39118"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cloudmagazin.com\/en\/wp-json\/wp\/v2\/categories?post=39118"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cloudmagazin.com\/en\/wp-json\/wp\/v2\/tags?post=39118"},{"taxonomy":"industry","embeddable":true,"href":"https:\/\/www.cloudmagazin.com\/en\/wp-json\/wp\/v2\/industry?post=39118"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}