{"id":39122,"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-08-03T16:06:57","modified_gmt":"2026-08-03T14:06:57","slug":"kubernetes-1-36-migration-enterprise-checkliste-cgroup-v2","status":"publish","type":"post","link":"https:\/\/www.cloudmagazin.com\/fr\/2026\/05\/03\/kubernetes-1-36-migration-enterprise-checkliste-cgroup-v2\/","title":{"rendered":"Migration K8s 1.36 : checklist cluster post-cgroup-v1 &amp; DRA"},"content":{"rendered":"<p style=\"color:#6190a9;font-size:0.9em;margin:0 0 16px;\">8 min de lecture<\/p>\n<p><strong>Kubernetes 1.36 est pass\u00e9 en disponibilit\u00e9 g\u00e9n\u00e9rale (GA) le 22 avril 2026. Deux changements sont au c\u0153ur de cette version : la suppression d\u00e9finitive du support cgroup-v1 et la disponibilit\u00e9 g\u00e9n\u00e9rale de l&rsquo;allocation dynamique des ressources (DRA). Pour les \u00e9quipes Ops en entreprise, cela se traduit par des t\u00e2ches concr\u00e8tes \u00e0 r\u00e9aliser dans les 60 prochains jours \u2013 avant que le support upstream et les correctifs de s\u00e9curit\u00e9 pour les anciennes versions de cluster n&rsquo;expirent. Voici une checklist de migration sans surcharge th\u00e9orique.<\/strong><\/p>\n<h2 style=\"margin-top:32px;margin-bottom:16px;\">Les points cl\u00e9s en bref<\/h2>\n<div style=\"background:#f8fbfd;border:1px solid rgba(11,183,253,0.28);border-radius:8px;padding:22px 26px;margin:16px 0 32px 0;\">\n<ul style=\"color:#1a2733\">\n<li>Kubernetes 1.36 GA le 22\/04\/2026 : suppression du support cgroup-v1, DRA devient disponible g\u00e9n\u00e9ralement<\/li>\n<li>Ceux qui fonctionnent encore sur cgroup-v1 (identifiable par <span style=\"font-family:monospace;background:#f4f4f4;padding:1px 5px;border-radius:3px;font-size:0.92em;\">&#8211;cgroup-driver=cgroupfs<\/span>) doivent migrer vers containerd + cgroup-v2 avant la mise \u00e0 niveau<\/li>\n<li>DRA-GA : l&rsquo;installation des pilotes de ressources et les CRD NodeFeature sont d\u00e9sormais obligatoires pour les charges de travail GPU\/FPGA<\/li>\n<li>Pr\u00e9requis minimum containerd : 1.7.x pour le support 1.36, 2.0 recommand\u00e9<\/li>\n<li>Fen\u00eatre de temps : Kubernetes 1.33 fin de vie en octobre 2026 &#8211; ceux qui sont encore sur 1.33 doivent mettre \u00e0 niveau maintenant<\/li>\n<\/ul>\n<\/div>\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;\">Articles li\u00e9s<\/span><a href=\"https:\/\/www.cloudmagazin.com\/fr\/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 en test pratique<\/a>&nbsp;&nbsp;<span style=\"color:#ccc;\">\/<\/span>&nbsp;&nbsp;FinOps 2026 : Ma\u00eetriser les co\u00fbts cloud en entreprise<\/p>\n<h2 style=\"margin-top:64px;margin-bottom:20px;padding-top:16px;\">Qu&rsquo;est-ce que Kubernetes 1.36 et pourquoi cette version est-elle critique pour la migration ?<\/h2>\n<p><strong>Qu&rsquo;est-ce que Kubernetes 1.36 ?<\/strong> Kubernetes 1.36 est la version publi\u00e9e le 22 avril 2026 du syst\u00e8me open source d&rsquo;orchestration de conteneurs, marquant la suppression d\u00e9finitive du support cgroup-v1 ainsi que la disponibilit\u00e9 g\u00e9n\u00e9rale de l&rsquo;allocation dynamique des ressources (DRA) pour les ressources mat\u00e9rielles telles que les GPU et les FPGA.<\/p>\n<p>Kubernetes 1.36 est la premi\u00e8re version \u00e0 supprimer compl\u00e8tement cgroup-v1. cgroup v1 (Control Groups version 1) \u00e9tait l&rsquo;interface classique du noyau Linux pour l&rsquo;isolation des ressources \u2013 limites de RAM, quotas CPU, hi\u00e9rarchies de processus. Depuis Kubernetes 1.25, cgroup-v2 \u00e9tait la voie standard. Avec la version 1.36, cgroup-v1 n&rsquo;est plus simplement d\u00e9pr\u00e9ci\u00e9 de mani\u00e8re optionnelle, il a disparu.<\/p>\n<p>Cela signifie : quiconque exploite encore un n\u0153ud avec le pilote cgroupfs sous cgroup-v1 ne pourra plus d\u00e9marrer apr\u00e8s une mise \u00e0 niveau vers 1.36. Le Kubelet renverra une erreur lors de la v\u00e9rification d&rsquo;initialisation. Il ne s&rsquo;agit pas d&rsquo;une transition douce \u2013 c&rsquo;est un arr\u00eat brutal.<\/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;\">Chiffres cl\u00e9s de la migration<\/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;\">des clusters d&rsquo;entreprise fonctionnaient encore sur cgroup-v1 ou avaient un statut incertain selon l&rsquo;enqu\u00eate CNCF T1 2026<\/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 Fin de vie &#8211; ceux qui sont encore sur 1.33 ont 5 mois<\/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;\">Version recommand\u00e9e pour K8s 1.36 &#8211; 1.7.x est le minimum, 2.0 est la voie support\u00e9e<\/p>\n<\/div>\n<\/div>\n<\/div>\n<h2 style=\"margin-top:64px;margin-bottom:20px;padding-top:16px;\">\u00c9tape 1 : V\u00e9rifier l&rsquo;\u00e9tat du cluster (version cgroup et containerd)<\/h2>\n<p>Avant que quiconque ne proc\u00e8de \u00e0 une mise \u00e0 niveau, chaque n\u0153ud doit faire un inventaire. Deux v\u00e9rifications, toutes deux r\u00e9alisables \u00e0 distance via kubectl :<\/p>\n<p><strong>Version de cgroup par n\u0153ud :<\/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=\u00a0\u00bbNAME:.metadata.name\u00a0\u00bb | \\<br \/>\n&nbsp;&nbsp;xargs -I{} kubectl describe node {} | grep \u00ab\u00a0Container Runtime\u00a0\u00bb<\/p>\n<p>&num; Ou directement sur le n\u0153ud :<br \/>\nstat -fc %T \/sys\/fs\/cgroup<br \/>\n&num; Sortie \u00ab\u00a0tmpfs\u00a0\u00bb = cgroup-v1, \u00ab\u00a0cgroup2fs\u00a0\u00bb = cgroup-v2\n<\/div>\n<p><strong>Version et configuration de containerd :<\/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 \/>\n&num; Min : 1.7.x | Recommand\u00e9 : 2.0.x<\/p>\n<p>&num; V\u00e9rifier le pilote cgroup de containerd :<br \/>\ngrep -i cgroup \/etc\/containerd\/config.toml<br \/>\n&num; Doit afficher \u00ab\u00a0SystemdCgroup = true\u00a0\u00bb (cgroup-v2)\n<\/div>\n<p>Celui qui voit <span style=\"font-family:monospace;background:#f4f4f4;padding:1px 5px;border-radius:3px;font-size:0.92em;\">SystemdCgroup = false<\/span> ou aucune entr\u00e9e fonctionne encore en mode cgroupfs. C&rsquo;est le principal obstacle \u00e0 la mise \u00e0 niveau vers la version 1.36.<\/p>\n<h2 style=\"margin-top:64px;margin-bottom:20px;padding-top:16px;\">\u00c9tape 2 : Migration vers cgroup-v2 au niveau des n\u0153uds<\/h2>\n<p>La migration des n\u0153uds de cgroup-v1 vers cgroup-v2 n\u00e9cessite un changement de param\u00e8tre du noyau et un cycle de red\u00e9marrage avec vidage du n\u0153ud (drain). Aucune mise \u00e0 niveau progressive (rolling upgrade) n&rsquo;est possible ; chaque n\u0153ud doit \u00eatre vid\u00e9.<\/p>\n<p><strong>1. Ajuster les param\u00e8tres de d\u00e9marrage du noyau<\/strong> (GRUB ou systemd-boot selon le syst\u00e8me d&rsquo;exploitation) :<\/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&num; \/etc\/default\/grub &#8211; d\u00e9sactiver cgroup-v1 :<br \/>\nGRUB_CMDLINE_LINUX=\u00a0\u00bbsystemd.unified_cgroup_hierarchy=1 cgroup_no_v1=all\u00a0\u00bb<\/p>\n<p>update-grub &#038;&#038; reboot\n<\/p><\/div>\n<p><strong>2. Mettre \u00e0 jour la configuration de containerd :<\/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&num; \/etc\/containerd\/config.toml<br \/>\n[plugins.\u00a0\u00bbio.containerd.grpc.v1.cri\u00a0\u00bb.containerd.runtimes.runc.options]<br \/>\n&nbsp;&nbsp;SystemdCgroup = true\n<\/div>\n<p><strong>3. Ajuster la configuration de Kubelet :<\/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&num; kubelet-config.yaml<br \/>\ncgroupDriver: systemd<\/p>\n<p>&num; S\u00e9quence de red\u00e9marrage :<br \/>\nkubectl drain &lt;n\u0153ud&gt; &#8211;ignore-daemonsets<br \/>\nsystemctl restart containerd kubelet<br \/>\nkubectl uncordon &lt;n\u0153ud&gt;\n<\/div>\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;\">\/\/ Propos<\/div>\n<p style=\"margin:0;font-size:1.15em;line-height:1.6;color:#f2fafd;font-weight:500;position:relative;\">Un n\u0153ud qui ne red\u00e9marre pas proprement apr\u00e8s le vidage, c&rsquo;est le moment o\u00f9 la planification se heurte \u00e0 la r\u00e9alit\u00e9. Pr\u00e9voyez 45 minutes par n\u0153ud, pas 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 style=\"margin-top:64px;margin-bottom:20px;padding-top:16px;\">\u00c9tape 3 : Configurer DRA &#8211; Dynamic Resource Allocation<\/h2>\n<p>DRA est d\u00e9sormais en disponibilit\u00e9 g\u00e9n\u00e9rale dans la version 1.36. Qu&rsquo;est-ce que cela signifie pour les \u00e9quipes g\u00e9rant des charges de travail GPU ou FPGA ? DRA remplace l&rsquo;ancien m\u00e9canisme de plugin de p\u00e9riph\u00e9rique pour les ressources mat\u00e9rielles. Si vous utilisez des GPU NVIDIA via le plugin de p\u00e9riph\u00e9rique NVIDIA, vous devez v\u00e9rifier si le pilote du fournisseur est d\u00e9j\u00e0 compatible avec DRA.<\/p>\n<p>V\u00e9rifications obligatoires pour DRA dans les environnements GPU :<\/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&num; V\u00e9rifier si le porteur de fonctionnalit\u00e9 DRA est actif :<br \/>\nkubectl get &#8211;raw \/api\/v1 | grep -i \u00ab\u00a0dynamic\u00a0\u00bb<\/p>\n<p>&num; V\u00e9rifier les CRDs ResourceSlice et DeviceClass :<br \/>\nkubectl get crd | grep resource.k8s.io<br \/>\n&num; Sortie attendue :<br \/>\n&num; deviceclasses.resource.k8s.io<br \/>\n&num; resourceclaims.resource.k8s.io<br \/>\n&num; resourceslices.resource.k8s.io\n<\/div>\n<p>NVIDIA a introduit le support DRA avec NVIDIA-GPU-Operator 25.x. Le support DRA pour AMD ROCm est annonc\u00e9 pour le deuxi\u00e8me trimestre 2026. Si vous utilisez des GPU Intel (Gaudi, Arc), vous devez effectuer des v\u00e9rifications s\u00e9par\u00e9es ; les Extensions Kubernetes d&rsquo;Intel ont leur propre cycle de publication.<\/p>\n<h2 style=\"margin-top:64px;margin-bottom:20px;padding-top:16px;\">Avantages et inconv\u00e9nients : passer directement \u00e0 1.36 ou faire une \u00e9tape interm\u00e9diaire 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;\">Arguments pour le passage direct \u00e0 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;\">Une seule migration au lieu de deux (pas de version interm\u00e9diaire)<\/li>\n<li style=\"margin-bottom:6px;\">DRA-GA imm\u00e9diatement utilisable<\/li>\n<li style=\"margin-bottom:6px;\">Horizon de support plus long (fin de vie de 1.36 : ~avril 2027)<\/li>\n<li style=\"margin-bottom:6px;\">Une seule fen\u00eatre d&rsquo;indisponibilit\u00e9 au lieu de deux<\/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;\">Arguments pour l&rsquo;\u00e9tape interm\u00e9diaire 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;\">Migration cgroup-v2 pr\u00e9parable en 1.35 sans les modifications de 1.36<\/li>\n<li style=\"margin-bottom:6px;\">DRA encore en beta en 1.35 &#8211; moins de surprises s&rsquo;il n&rsquo;y a pas de charge GPU<\/li>\n<li style=\"margin-bottom:6px;\">R\u00e9partition des risques : migration infrastructure + mise \u00e0 jour API s\u00e9par\u00e9es<\/li>\n<\/ul>\n<\/div>\n<\/div>\n<h2 style=\"padding-top:64px;margin-bottom:20px;\">Foire aux questions<\/h2>\n<details style=\"margin-bottom:12px;\">\n<summary><strong>Dois-je activer cgroup-v2 avant de mettre \u00e0 niveau vers K8s 1.36 ?<\/strong><\/summary>\n<p>Oui, c&rsquo;est une exigence stricte. K8s 1.36 ne d\u00e9marre pas sur les n\u0153uds qui fonctionnent encore en mode cgroup-v1. La migration doit \u00eatre termin\u00e9e au niveau du n\u0153ud avant la mise \u00e0 niveau Kubernetes (param\u00e8tres GRUB + configuration containerd + config Kubelet).<\/p>\n<\/details>\n<details style=\"margin-bottom:12px;\">\n<summary><strong>Quelle version de containerd me faut-il pour Kubernetes 1.36 ?<\/strong><\/summary>\n<p>Le minimum est containerd 1.7.x. Il est recommand\u00e9 d&rsquo;utiliser containerd 2.0.x pour un support complet. containerd 1.6.x n&rsquo;est plus compatible. V\u00e9rifiez avec <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>DRA remplace-t-il NVIDIA Device Plugin ?<\/strong><\/summary>\n<p>\u00c0 moyen terme oui, \u00e0 court terme les deux coexistent. DRA est en GA d\u00e8s K8s 1.36, mais les pilotes des fabricants ont leurs propres feuilles de route. NVIDIA GPU Operator prend en charge DRA \u00e0 partir de la version 25.x. Le Device Plugin continue de fonctionner en parall\u00e8le jusqu&rsquo;\u00e0 ce que les fabricants basculent officiellement vers DRA uniquement.<\/p>\n<\/details>\n<details style=\"margin-bottom:12px;\">\n<summary><strong>Que deviennent mes quotas de ressources existants apr\u00e8s la migration vers cgroup-v2 ?<\/strong><\/summary>\n<p>Les limites m\u00e9moire et CPU restent s\u00e9mantiquement identiques sous cgroup-v2. La diff\u00e9rence : cgroup-v2 applique les limites plus pr\u00e9cis\u00e9ment, notamment dans les sc\u00e9narios de sur-engagement m\u00e9moire. Dans de rares cas, les charges de travail qui fonctionnaient \u00e0 la limite sous cgroup-v1 peuvent recevoir des signaux OOM plus t\u00f4t sous cgroup-v2.<\/p>\n<\/details>\n<details style=\"margin-bottom:12px;\">\n<summary><strong>Comment v\u00e9rifier si mon service Kubernetes manag\u00e9 (EKS, GKE, AKS) utilise d\u00e9j\u00e0 cgroup-v2 ?<\/strong><\/summary>\n<p>EKS : Amazon Linux 2023 utilise cgroup-v2 par d\u00e9faut. Amazon Linux 2 reste en cgroup-v1. GKE : Tous les n\u0153uds avec Container-Optimized OS depuis 2023 sont en cgroup-v2. AKS : Les n\u0153uds Ubuntu standard passent \u00e0 cgroup-v2 \u00e0 partir d&rsquo;AKS 1.25. V\u00e9rifiez avec <span style=\"font-family:monospace;background:#f4f4f4;padding:1px 5px;border-radius:3px;font-size:0.92em;\">stat -fc %T \/sys\/fs\/cgroup<\/span> sur un n\u0153ud.<\/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;\">R\u00e9seau<\/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;\">Industrie 5.0 : Ce que les CIO doivent d\u00e9cider maintenant<\/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 : Cadre d\u00e9cisionnel<\/a> &nbsp;(MyBusinessFuture)<\/p>\n<\/div>\n<p style=\"color:#888;font-size:0.85em;text-align:right;font-style:italic;\">Source image de couverture : Pexels \/ cottonbro studio (px:6804597)<\/p>\n","protected":false},"excerpt":{"rendered":"Kubernetes 1.36 supprime le support de cgroup-v1 et met DRA en disponibilit\u00e9 g\u00e9n\u00e9rale.","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_slot_owner":"","_evm_translation_lang":"","featured_post":0,"featured_post_sortierung":0,"_wp_old_slug":[],"footnotes":""},"categories":[942],"tags":[],"industry":[],"class_list":["post-39122","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-guides"],"evm_reading_time_minutes":8,"wpml_language":"fr","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>Migration Kubernetes 1.36 : la checklist cluster pour les \u00e9quipes enterprise apr<\/title>\n<meta name=\"description\" content=\"Guide de migration Kubernetes 1.36 : suppression de cgroup-v1, DRA GA. Liste de contr\u00f4le \u00e9tape par \u00e9tape pour les \u00e9quipes d&#039;entreprise \u2013 du contr\u00f4le\u2026\" \/>\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\/fr\/2026\/05\/03\/kubernetes-1-36-migration-enterprise-checkliste-cgroup-v2\/\" \/>\n<meta property=\"og:locale\" content=\"fr_FR\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Migration Kubernetes 1.36 : la checklist cluster pour les \u00e9quipes enterprise apr\" \/>\n<meta property=\"og:description\" content=\"Guide de migration Kubernetes 1.36 : suppression de cgroup-v1, DRA GA. Liste de contr\u00f4le \u00e9tape par \u00e9tape pour les \u00e9quipes d&#039;entreprise \u2013 du contr\u00f4le\u2026\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.cloudmagazin.com\/fr\/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-08-03T14:06:57+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=\"\u00c9crit par\" \/>\n\t<meta name=\"twitter:data1\" content=\"Alec Chizhik\" \/>\n\t<meta name=\"twitter:label2\" content=\"Dur\u00e9e de lecture estim\u00e9e\" \/>\n\t<meta name=\"twitter:data2\" content=\"7 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"NewsArticle\",\"@id\":\"https:\\\/\\\/www.cloudmagazin.com\\\/fr\\\/2026\\\/05\\\/03\\\/kubernetes-1-36-migration-enterprise-checkliste-cgroup-v2\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.cloudmagazin.com\\\/fr\\\/2026\\\/05\\\/03\\\/kubernetes-1-36-migration-enterprise-checkliste-cgroup-v2\\\/\"},\"author\":{\"name\":\"Alec Chizhik\",\"@id\":\"https:\\\/\\\/www.cloudmagazin.com\\\/fr\\\/#\\\/schema\\\/person\\\/ce38baaa19a580268aedce096597eb3c\"},\"headline\":\"Migration K8s 1.36 : checklist cluster post-cgroup-v1 &amp; DRA\",\"datePublished\":\"2026-05-03T11:37:11+00:00\",\"dateModified\":\"2026-08-03T14:06:57+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.cloudmagazin.com\\\/fr\\\/2026\\\/05\\\/03\\\/kubernetes-1-36-migration-enterprise-checkliste-cgroup-v2\\\/\"},\"wordCount\":1397,\"publisher\":{\"@id\":\"https:\\\/\\\/www.cloudmagazin.com\\\/fr\\\/#organization\"},\"image\":{\"@id\":\"https:\\\/\\\/www.cloudmagazin.com\\\/fr\\\/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\":\"fr-FR\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.cloudmagazin.com\\\/fr\\\/2026\\\/05\\\/03\\\/kubernetes-1-36-migration-enterprise-checkliste-cgroup-v2\\\/\",\"url\":\"https:\\\/\\\/www.cloudmagazin.com\\\/fr\\\/2026\\\/05\\\/03\\\/kubernetes-1-36-migration-enterprise-checkliste-cgroup-v2\\\/\",\"name\":\"Migration Kubernetes 1.36 : la checklist cluster pour les \u00e9quipes enterprise apr\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.cloudmagazin.com\\\/fr\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/www.cloudmagazin.com\\\/fr\\\/2026\\\/05\\\/03\\\/kubernetes-1-36-migration-enterprise-checkliste-cgroup-v2\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/www.cloudmagazin.com\\\/fr\\\/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-08-03T14:06:57+00:00\",\"description\":\"Guide de migration Kubernetes 1.36 : suppression de cgroup-v1, DRA GA. Liste de contr\u00f4le \u00e9tape par \u00e9tape pour les \u00e9quipes d'entreprise \u2013 du contr\u00f4le\u2026\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.cloudmagazin.com\\\/fr\\\/2026\\\/05\\\/03\\\/kubernetes-1-36-migration-enterprise-checkliste-cgroup-v2\\\/#breadcrumb\"},\"inLanguage\":\"fr-FR\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.cloudmagazin.com\\\/fr\\\/2026\\\/05\\\/03\\\/kubernetes-1-36-migration-enterprise-checkliste-cgroup-v2\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"fr-FR\",\"@id\":\"https:\\\/\\\/www.cloudmagazin.com\\\/fr\\\/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\\\/fr\\\/2026\\\/05\\\/03\\\/kubernetes-1-36-migration-enterprise-checkliste-cgroup-v2\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/www.cloudmagazin.com\\\/fr\\\/accueil\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Migration K8s 1.36 : checklist cluster post-cgroup-v1 &amp; DRA\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.cloudmagazin.com\\\/fr\\\/#website\",\"url\":\"https:\\\/\\\/www.cloudmagazin.com\\\/fr\\\/\",\"name\":\"cloudmagazin\",\"description\":\"Inspiration f\u00fcr Businessentscheider\",\"publisher\":{\"@id\":\"https:\\\/\\\/www.cloudmagazin.com\\\/fr\\\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.cloudmagazin.com\\\/fr\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"fr-FR\"},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/www.cloudmagazin.com\\\/fr\\\/#organization\",\"name\":\"cloudmagazin\",\"url\":\"https:\\\/\\\/www.cloudmagazin.com\\\/fr\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"fr-FR\",\"@id\":\"https:\\\/\\\/www.cloudmagazin.com\\\/fr\\\/#\\\/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\\\/fr\\\/#\\\/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\\\/fr\\\/#\\\/schema\\\/person\\\/ce38baaa19a580268aedce096597eb3c\",\"name\":\"Alec Chizhik\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"fr-FR\",\"@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 est le directeur num\u00e9rique chez Evernine et \u00e9crit sur les architectures cloud, la cybers\u00e9curit\u00e9 et les pratiques op\u00e9rationnelles num\u00e9riques.\",\"sameAs\":[\"https:\\\/\\\/www.linkedin.com\\\/in\\\/alecchizhik\\\/\"],\"url\":\"https:\\\/\\\/www.cloudmagazin.com\\\/fr\\\/author\\\/alec\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Migration Kubernetes 1.36 : la checklist cluster pour les \u00e9quipes enterprise apr","description":"Guide de migration Kubernetes 1.36 : suppression de cgroup-v1, DRA GA. Liste de contr\u00f4le \u00e9tape par \u00e9tape pour les \u00e9quipes d'entreprise \u2013 du contr\u00f4le\u2026","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\/fr\/2026\/05\/03\/kubernetes-1-36-migration-enterprise-checkliste-cgroup-v2\/","og_locale":"fr_FR","og_type":"article","og_title":"Migration Kubernetes 1.36 : la checklist cluster pour les \u00e9quipes enterprise apr","og_description":"Guide de migration Kubernetes 1.36 : suppression de cgroup-v1, DRA GA. Liste de contr\u00f4le \u00e9tape par \u00e9tape pour les \u00e9quipes d'entreprise \u2013 du contr\u00f4le\u2026","og_url":"https:\/\/www.cloudmagazin.com\/fr\/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-08-03T14:06:57+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":{"\u00c9crit par":"Alec Chizhik","Dur\u00e9e de lecture estim\u00e9e":"7 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"NewsArticle","@id":"https:\/\/www.cloudmagazin.com\/fr\/2026\/05\/03\/kubernetes-1-36-migration-enterprise-checkliste-cgroup-v2\/#article","isPartOf":{"@id":"https:\/\/www.cloudmagazin.com\/fr\/2026\/05\/03\/kubernetes-1-36-migration-enterprise-checkliste-cgroup-v2\/"},"author":{"name":"Alec Chizhik","@id":"https:\/\/www.cloudmagazin.com\/fr\/#\/schema\/person\/ce38baaa19a580268aedce096597eb3c"},"headline":"Migration K8s 1.36 : checklist cluster post-cgroup-v1 &amp; DRA","datePublished":"2026-05-03T11:37:11+00:00","dateModified":"2026-08-03T14:06:57+00:00","mainEntityOfPage":{"@id":"https:\/\/www.cloudmagazin.com\/fr\/2026\/05\/03\/kubernetes-1-36-migration-enterprise-checkliste-cgroup-v2\/"},"wordCount":1397,"publisher":{"@id":"https:\/\/www.cloudmagazin.com\/fr\/#organization"},"image":{"@id":"https:\/\/www.cloudmagazin.com\/fr\/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":"fr-FR"},{"@type":"WebPage","@id":"https:\/\/www.cloudmagazin.com\/fr\/2026\/05\/03\/kubernetes-1-36-migration-enterprise-checkliste-cgroup-v2\/","url":"https:\/\/www.cloudmagazin.com\/fr\/2026\/05\/03\/kubernetes-1-36-migration-enterprise-checkliste-cgroup-v2\/","name":"Migration Kubernetes 1.36 : la checklist cluster pour les \u00e9quipes enterprise apr","isPartOf":{"@id":"https:\/\/www.cloudmagazin.com\/fr\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.cloudmagazin.com\/fr\/2026\/05\/03\/kubernetes-1-36-migration-enterprise-checkliste-cgroup-v2\/#primaryimage"},"image":{"@id":"https:\/\/www.cloudmagazin.com\/fr\/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-08-03T14:06:57+00:00","description":"Guide de migration Kubernetes 1.36 : suppression de cgroup-v1, DRA GA. Liste de contr\u00f4le \u00e9tape par \u00e9tape pour les \u00e9quipes d'entreprise \u2013 du contr\u00f4le\u2026","breadcrumb":{"@id":"https:\/\/www.cloudmagazin.com\/fr\/2026\/05\/03\/kubernetes-1-36-migration-enterprise-checkliste-cgroup-v2\/#breadcrumb"},"inLanguage":"fr-FR","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.cloudmagazin.com\/fr\/2026\/05\/03\/kubernetes-1-36-migration-enterprise-checkliste-cgroup-v2\/"]}]},{"@type":"ImageObject","inLanguage":"fr-FR","@id":"https:\/\/www.cloudmagazin.com\/fr\/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\/fr\/2026\/05\/03\/kubernetes-1-36-migration-enterprise-checkliste-cgroup-v2\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.cloudmagazin.com\/fr\/accueil\/"},{"@type":"ListItem","position":2,"name":"Migration K8s 1.36 : checklist cluster post-cgroup-v1 &amp; DRA"}]},{"@type":"WebSite","@id":"https:\/\/www.cloudmagazin.com\/fr\/#website","url":"https:\/\/www.cloudmagazin.com\/fr\/","name":"cloudmagazin","description":"Inspiration f\u00fcr Businessentscheider","publisher":{"@id":"https:\/\/www.cloudmagazin.com\/fr\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.cloudmagazin.com\/fr\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"fr-FR"},{"@type":"Organization","@id":"https:\/\/www.cloudmagazin.com\/fr\/#organization","name":"cloudmagazin","url":"https:\/\/www.cloudmagazin.com\/fr\/","logo":{"@type":"ImageObject","inLanguage":"fr-FR","@id":"https:\/\/www.cloudmagazin.com\/fr\/#\/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\/fr\/#\/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\/fr\/#\/schema\/person\/ce38baaa19a580268aedce096597eb3c","name":"Alec Chizhik","image":{"@type":"ImageObject","inLanguage":"fr-FR","@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 est le directeur num\u00e9rique chez Evernine et \u00e9crit sur les architectures cloud, la cybers\u00e9curit\u00e9 et les pratiques op\u00e9rationnelles num\u00e9riques.","sameAs":["https:\/\/www.linkedin.com\/in\/alecchizhik\/"],"url":"https:\/\/www.cloudmagazin.com\/fr\/author\/alec\/"}]}},"_links":{"self":[{"href":"https:\/\/www.cloudmagazin.com\/fr\/wp-json\/wp\/v2\/posts\/39122","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.cloudmagazin.com\/fr\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.cloudmagazin.com\/fr\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.cloudmagazin.com\/fr\/wp-json\/wp\/v2\/users\/31"}],"replies":[{"embeddable":true,"href":"https:\/\/www.cloudmagazin.com\/fr\/wp-json\/wp\/v2\/comments?post=39122"}],"version-history":[{"count":5,"href":"https:\/\/www.cloudmagazin.com\/fr\/wp-json\/wp\/v2\/posts\/39122\/revisions"}],"predecessor-version":[{"id":50592,"href":"https:\/\/www.cloudmagazin.com\/fr\/wp-json\/wp\/v2\/posts\/39122\/revisions\/50592"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.cloudmagazin.com\/fr\/wp-json\/wp\/v2\/media\/39112"}],"wp:attachment":[{"href":"https:\/\/www.cloudmagazin.com\/fr\/wp-json\/wp\/v2\/media?parent=39122"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cloudmagazin.com\/fr\/wp-json\/wp\/v2\/categories?post=39122"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cloudmagazin.com\/fr\/wp-json\/wp\/v2\/tags?post=39122"},{"taxonomy":"industry","embeddable":true,"href":"https:\/\/www.cloudmagazin.com\/fr\/wp-json\/wp\/v2\/industry?post=39122"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}