<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: kubernetes</title>
    <description>The latest articles tagged 'kubernetes' on DEV Community.</description>
    <link>https://dev.to/t/kubernetes</link>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/tag/kubernetes"/>
    <language>en</language>
    <item>
      <title>NVIDIA Run:ai: Orquestração de Cargas de Trabalho de IA</title>
      <dc:creator>Victor Hugo</dc:creator>
      <pubDate>Wed, 18 Nov 2026 03:05:33 +0000</pubDate>
      <link>https://dev.to/victor_hugo_a07c85ac09eea/nvidia-runai-orquestracao-de-cargas-de-trabalho-de-ia-392j</link>
      <guid>https://dev.to/victor_hugo_a07c85ac09eea/nvidia-runai-orquestracao-de-cargas-de-trabalho-de-ia-392j</guid>
      <description>&lt;h3&gt;
  
  
  O que é
&lt;/h3&gt;

&lt;p&gt;O NVIDIA Run:ai é uma plataforma de código aberto para orquestração de GPUs e cargas de trabalho de IA que opera sobre o Kubernetes. Ele não substitui o Kubernetes, mas o estende, oferecendo capacidades de agendamento sensíveis a GPUs, governança e observabilidade. A ferramenta estrutura-se em dois componentes: o plano de controle, que centraliza a gestão de recursos e monitoramento, e os serviços de cluster, que aplicam o agendamento e a gestão de cargas de trabalho em cada cluster Kubernetes conectado.&lt;/p&gt;

&lt;h3&gt;
  
  
  Para quem serve
&lt;/h3&gt;

&lt;p&gt;A plataforma é ideal para organizações que gerenciam infraestruturas de IA compartilhadas em ambientes on-premises, na nuvem ou híbridos. Serve para equipes que precisam de eficiência na distribuição de GPUs entre diversos projetos e departamentos, permitindo o uso de cotas de recursos e alocação dinâmica, inclusive com GPUs fracionárias. É útil para quem opera fluxos de desenvolvimento, treinamento distribuído e inferência, buscando funcionalidades como &lt;em&gt;fair-share&lt;/em&gt;, preempção e controle de acesso baseado em funções.&lt;/p&gt;

&lt;h3&gt;
  
  
  Como começar
&lt;/h3&gt;

&lt;p&gt;A implementação exige um cluster Kubernetes ou OpenShift. O acesso ao software é feito via monorepo, que disponibiliza o instalador, a interface de linha de comando (CLI), pacotes de cliente e o ambiente de desenvolvimento local. A operação do sistema pode ser realizada através da interface web, da CLI ou via API REST. Para a instalação e configuração inicial, recomenda-se consultar a documentação oficial e o guia de contribuição disponíveis no repositório.&lt;/p&gt;

&lt;h2&gt;
  
  
  Instalação
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;./local-dev.sh                                  &lt;span class="c"&gt;# full build + cluster + deploy&lt;/span&gt;
./local-dev.sh --skip-build --skip-cluster      &lt;span class="c"&gt;# re-deploy only&lt;/span&gt;
./local-dev.sh --teardown                       &lt;span class="c"&gt;# tear the environment down&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;🔗 Repositório oficial: &lt;a href="https://github.com/dsx-ai-factory/run-ai" rel="noopener noreferrer"&gt;https://github.com/dsx-ai-factory/run-ai&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Veja em 1 minuto
&lt;/h2&gt;

&lt;p&gt;  &lt;iframe src="https://www.youtube.com/embed/s7HDjCHCXVU" width="710" height="399"&gt;
  &lt;/iframe&gt;
&lt;/p&gt;

&lt;p&gt;📚 Mais conteúdos do canal: &lt;a href="https://gist.github.com/VictorHugodaSilvaSousa/d1e955e97cd27fc662351821d0a3fdbe" rel="noopener noreferrer"&gt;https://gist.github.com/VictorHugodaSilvaSousa/d1e955e97cd27fc662351821d0a3fdbe&lt;/a&gt;&lt;/p&gt;

</description>
      <category>braziliandevs</category>
      <category>opensource</category>
      <category>github</category>
      <category>kubernetes</category>
    </item>
    <item>
      <title>Java4Shell CVE-2026-114938: Is Your Server Next? Find Every Vulnerable JVM</title>
      <dc:creator>GDS K S</dc:creator>
      <pubDate>Wed, 18 Nov 2026 02:50:55 +0000</pubDate>
      <link>https://dev.to/thegdsks/java4shell-runbook-find-every-vulnerable-jvm-today-4ei0</link>
      <guid>https://dev.to/thegdsks/java4shell-runbook-find-every-vulnerable-jvm-today-4ei0</guid>
      <description>&lt;h1&gt;
  
  
  Java4Shell CVE-2026-114938: Is Your Server Next? Find Every Vulnerable JVM
&lt;/h1&gt;

&lt;p&gt;CVE-2026-114938 (Java4Shell) is a heap out-of-bounds write in OpenJDK's AVX-512 Base64 decoder. I covered the background in a separate post. This one is the runbook: how to find the JVMs that matter, what to run, what to change and how to prove it worked.&lt;/p&gt;

&lt;p&gt;I have not run this against a vulnerable machine. The commands come from the Qualys, Upwind, Endor Labs and Equixly write-ups, and I only checked that the shell and Java snippets parse. Test in staging first.&lt;/p&gt;

&lt;h2&gt;
  
  
  TL;DR
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Step&lt;/th&gt;
&lt;th&gt;Goal&lt;/th&gt;
&lt;th&gt;Time&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;1. Inventory&lt;/td&gt;
&lt;td&gt;Find the real runtime behind every Java process&lt;/td&gt;
&lt;td&gt;minutes per host&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;2. Hardware check&lt;/td&gt;
&lt;td&gt;Split hosts by AVX-512 VBMI&lt;/td&gt;
&lt;td&gt;seconds&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;3. Patch&lt;/td&gt;
&lt;td&gt;Move to a vendor build that carries the fix&lt;/td&gt;
&lt;td&gt;your restart window&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;4. Mitigate&lt;/td&gt;
&lt;td&gt;Apply a JVM flag where you cannot patch&lt;/td&gt;
&lt;td&gt;one restart&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;5. Verify&lt;/td&gt;
&lt;td&gt;Prove the flag or build is live in the running process&lt;/td&gt;
&lt;td&gt;seconds&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;6. Watch&lt;/td&gt;
&lt;td&gt;Alert on crash and decode patterns&lt;/td&gt;
&lt;td&gt;ongoing&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h2&gt;
  
  
  1. Inventory the JVM that actually runs
&lt;/h2&gt;

&lt;p&gt;Your shell's &lt;code&gt;java&lt;/code&gt; tells you very little. Jenkins, Jira, Confluence, Keycloak and Elasticsearch ship or select their own runtime. Equixly and Endor Labs both call this out. Ask the process.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="c"&gt;#!/usr/bin/env bash&lt;/span&gt;
&lt;span class="c"&gt;# jvm-inventory.sh: one line per running JVM with its real binary and version&lt;/span&gt;
&lt;span class="nb"&gt;set&lt;/span&gt; -u
&lt;span class="k"&gt;for&lt;/span&gt; pid &lt;span class="k"&gt;in&lt;/span&gt; &lt;span class="nv"&gt;$(&lt;/span&gt;pgrep -f &lt;span class="s1"&gt;'[j]ava'&lt;/span&gt;&lt;span class="o"&gt;)&lt;/span&gt;&lt;span class="o"&gt;;&lt;/span&gt; &lt;span class="k"&gt;do&lt;/span&gt;
  &lt;span class="nv"&gt;exe&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="nv"&gt;$(&lt;/span&gt;readlink -f &lt;span class="s2"&gt;"/proc/$pid/exe"&lt;/span&gt; 2&lt;span class="o"&gt;&amp;gt;&lt;/span&gt;/dev/null &lt;span class="o"&gt;||&lt;/span&gt; &lt;span class="nb"&gt;echo&lt;/span&gt; unknown&lt;span class="o"&gt;)&lt;/span&gt;
  &lt;span class="nv"&gt;ver&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="nv"&gt;$(&lt;/span&gt;jcmd &lt;span class="s2"&gt;"$pid"&lt;/span&gt; VM.version 2&lt;span class="o"&gt;&amp;gt;&lt;/span&gt;/dev/null &lt;span class="o"&gt;|&lt;/span&gt; grep -m1 -E &lt;span class="s1"&gt;'JDK|OpenJDK'&lt;/span&gt; &lt;span class="o"&gt;||&lt;/span&gt; &lt;span class="nb"&gt;echo&lt;/span&gt; &lt;span class="s2"&gt;"jcmd unavailable"&lt;/span&gt;&lt;span class="o"&gt;)&lt;/span&gt;
  &lt;span class="nb"&gt;printf&lt;/span&gt; &lt;span class="s1"&gt;'%s\t%s\t%s\n'&lt;/span&gt; &lt;span class="s2"&gt;"$pid"&lt;/span&gt; &lt;span class="s2"&gt;"$exe"&lt;/span&gt; &lt;span class="s2"&gt;"$ver"&lt;/span&gt;
&lt;span class="k"&gt;done&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;code&gt;jcmd&lt;/code&gt; must run as the same user as the target JVM. If it prints "jcmd unavailable", the process may be a minimal runtime without the JDK tools. Fall back to &lt;code&gt;"$exe" -version&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;Version triage, using the ranges Qualys and Upwind list.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Line&lt;/th&gt;
&lt;th&gt;Affected&lt;/th&gt;
&lt;th&gt;Fixed Oracle build&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;17&lt;/td&gt;
&lt;td&gt;17.0.6 and later, before the fix&lt;/td&gt;
&lt;td&gt;17.0.21.1&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;21&lt;/td&gt;
&lt;td&gt;up to 21.0.13&lt;/td&gt;
&lt;td&gt;21.0.13.1&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;25&lt;/td&gt;
&lt;td&gt;up to 25.0.5&lt;/td&gt;
&lt;td&gt;25.0.5.1&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;27&lt;/td&gt;
&lt;td&gt;up to 27.0.1&lt;/td&gt;
&lt;td&gt;27.0.1.1&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;8&lt;/td&gt;
&lt;td&gt;Oracle Enterprise Performance Pack 8u511b33-perf&lt;/td&gt;
&lt;td&gt;8u513-perf&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;11, 17.0.0 to 17.0.5, standard 8&lt;/td&gt;
&lt;td&gt;not affected&lt;/td&gt;
&lt;td&gt;none needed&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;A version number is not proof. Endor Labs warns that an LTS build with a matching number may still lack the commit, because the fix is tracked as JDK-8393212. Treat the vendor advisory as the source of truth, and note that Qualys lists Corretto 17.0.21.1.2 as released.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Check the hardware
&lt;/h2&gt;

&lt;p&gt;Only x86-64 hosts with AVX-512 VBMI reach the vulnerable routine. Run this on each host or container node.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;grep -m1 &lt;span class="s1"&gt;'^flags'&lt;/span&gt; /proc/cpuinfo &lt;span class="o"&gt;|&lt;/span&gt; tr &lt;span class="s1"&gt;' '&lt;/span&gt; &lt;span class="s1"&gt;'\n'&lt;/span&gt; &lt;span class="o"&gt;|&lt;/span&gt; grep -E &lt;span class="s1"&gt;'^(avx512f|avx512bw|avx512vbmi|bmi2)$'&lt;/span&gt; &lt;span class="o"&gt;|&lt;/span&gt; sort
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Per Qualys, you are on the hardware side of the risk only when all four flags appear. Intel Ice Lake and later server parts and AMD Zen 4 and later qualify. ARM64, including Graviton and Apple silicon, does not.&lt;/p&gt;

&lt;p&gt;In Kubernetes, pods inherit the node's CPU, so check the node and not the image.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="c"&gt;# Which nodes would run the vulnerable path&lt;/span&gt;
&lt;span class="k"&gt;for&lt;/span&gt; node &lt;span class="k"&gt;in&lt;/span&gt; &lt;span class="nv"&gt;$(&lt;/span&gt;kubectl get nodes -o name&lt;span class="o"&gt;)&lt;/span&gt;&lt;span class="o"&gt;;&lt;/span&gt; &lt;span class="k"&gt;do&lt;/span&gt;
  &lt;span class="nv"&gt;pod&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s2"&gt;"cpucheck-${node#node/}"&lt;/span&gt;
  kubectl debug &lt;span class="s2"&gt;"$node"&lt;/span&gt; -q --image=busybox --profile=general -- \
    sh -c &lt;span class="s2"&gt;"grep -m1 '^flags' /proc/cpuinfo | tr ' ' '\n' | grep -c avx512vbmi"&lt;/span&gt; 2&lt;span class="o"&gt;&amp;gt;&lt;/span&gt;/dev/null \
    &lt;span class="o"&gt;|&lt;/span&gt; sed &lt;span class="s2"&gt;"s|^|$node  avx512vbmi=|"&lt;/span&gt;
&lt;span class="k"&gt;done&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Remember Qualys's caution: a resize or an instance family change can move a workload onto an affected CPU later. A host that passes today is not a permanent pass.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Patch
&lt;/h2&gt;

&lt;p&gt;Patching is the only complete fix, and the vendors say so. The steps that bite people are all about the running process.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Rebuild container images from a base that carries the fixed JDK, then redeploy. Replacing files on disk does not change a JVM that is already running.&lt;/li&gt;
&lt;li&gt;Restart every Java process. Without a restart you have patched a file, not a process.&lt;/li&gt;
&lt;li&gt;For bundled runtimes, take the application vendor's update, not a hand-swapped JDK, unless the vendor documents it.&lt;/li&gt;
&lt;li&gt;For Temurin, Zulu, Microsoft, Red Hat and distro packages, confirm the fixed build in the vendor advisory. Equixly could not confirm those on November 17.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  4. Mitigate where you cannot patch yet
&lt;/h2&gt;

&lt;p&gt;Both Qualys and Upwind recommend one flag first.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;-XX:-UseBASE64Intrinsics
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;It turns off the fast decoder on any architecture. Qualys warns that large Base64 workloads may slow down, and Upwind reports it stopped the overflow on every affected version they tested. In a container, set it through the environment.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight docker"&gt;&lt;code&gt;&lt;span class="k"&gt;ENV&lt;/span&gt; &lt;span class="nv"&gt;JAVA_TOOL_OPTIONS&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s2"&gt;"-XX:-UseBASE64Intrinsics"&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Two alternatives appear in the write-ups, and each has a trap.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Flag&lt;/th&gt;
&lt;th&gt;Trap&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;-XX:UseAVX=2&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;Disables all AVX-512, so it can slow unrelated work. On ARM the JVM refuses to start.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;-XX:DisableIntrinsic=_base64_decodeBlock&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;Without &lt;code&gt;-XX:+UnlockDiagnosticVMOptions&lt;/code&gt; the JVM will not start. Pushed through &lt;code&gt;JAVA_TOOL_OPTIONS&lt;/code&gt;, Upwind calls it a fleet-wide outage.&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;A reverse proxy is not a control. Qualys says so plainly, and CISA's size-limit advice does not stop this bug on its own.&lt;/p&gt;

&lt;h2&gt;
  
  
  5. Verify in the running process
&lt;/h2&gt;

&lt;p&gt;Setting a flag in a manifest proves nothing until you ask the process.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="c"&gt;# Flag state inside a live JVM&lt;/span&gt;
jcmd &lt;span class="o"&gt;&amp;lt;&lt;/span&gt;pid&lt;span class="o"&gt;&amp;gt;&lt;/span&gt; VM.flags &lt;span class="o"&gt;|&lt;/span&gt; tr &lt;span class="s1"&gt;' '&lt;/span&gt; &lt;span class="s1"&gt;'\n'&lt;/span&gt; &lt;span class="o"&gt;|&lt;/span&gt; grep -E &lt;span class="s1"&gt;'UseBASE64Intrinsics|UseAVX'&lt;/span&gt;

&lt;span class="c"&gt;# Or ask a fresh JVM what it would do with your options&lt;/span&gt;
java -XX:+PrintFlagsFinal -version &lt;span class="o"&gt;|&lt;/span&gt; grep -E &lt;span class="s1"&gt;'UseAVX|UseBASE64Intrinsics'&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;You want &lt;code&gt;UseBASE64Intrinsics = false&lt;/code&gt; in the process. Remove the flag after the patch lands, because it costs speed.&lt;/p&gt;

&lt;h2&gt;
  
  
  6. A guard in your own code
&lt;/h2&gt;

&lt;p&gt;If you decode untrusted Base64 with &lt;code&gt;java.util.Base64&lt;/code&gt;, you can reject the malformed shape before the decoder sees it. Upwind's detection heuristic is a Base64-alphabet token of 32 or more characters that ends in &lt;code&gt;=&lt;/code&gt; and whose length is not a multiple of 4. Well-formed padded Base64 always has a length divisible by 4.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight java"&gt;&lt;code&gt;&lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="n"&gt;java&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;util&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nc"&gt;Base64&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;

&lt;span class="k"&gt;public&lt;/span&gt; &lt;span class="kd"&gt;final&lt;/span&gt; &lt;span class="k"&gt;class&lt;/span&gt; &lt;span class="nc"&gt;SafeBase64&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="k"&gt;private&lt;/span&gt; &lt;span class="nc"&gt;SafeBase64&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;

    &lt;span class="cm"&gt;/** Rejects padded input whose length cannot be valid Base64 before decoding. */&lt;/span&gt;
    &lt;span class="k"&gt;public&lt;/span&gt; &lt;span class="k"&gt;static&lt;/span&gt; &lt;span class="kt"&gt;byte&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt; &lt;span class="nf"&gt;decode&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="kt"&gt;String&lt;/span&gt; &lt;span class="n"&gt;input&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
        &lt;span class="k"&gt;if&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;input&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;endsWith&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s2"&gt;"="&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;&amp;amp;&amp;amp;&lt;/span&gt; &lt;span class="n"&gt;input&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;length&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;%&lt;/span&gt; &lt;span class="mi"&gt;4&lt;/span&gt; &lt;span class="o"&gt;!=&lt;/span&gt; &lt;span class="mi"&gt;0&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
            &lt;span class="k"&gt;throw&lt;/span&gt; &lt;span class="k"&gt;new&lt;/span&gt; &lt;span class="nc"&gt;IllegalArgumentException&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s2"&gt;"malformed base64 padding"&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
        &lt;span class="p"&gt;}&lt;/span&gt;
        &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="nc"&gt;Base64&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;getDecoder&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;decode&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;input&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
    &lt;span class="p"&gt;}&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;This is defense in depth. It narrows the input, and it does not replace the patch. I have not tested it against Calif's chains, which are unpublished.&lt;/p&gt;

&lt;h2&gt;
  
  
  7. Detection
&lt;/h2&gt;

&lt;p&gt;Endor Labs and Equixly suggest the same few signals.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Authorization headers or request fields where Base64 ends in &lt;code&gt;=&lt;/code&gt; or &lt;code&gt;==&lt;/code&gt; and the length is not a multiple of 4. Equixly offers a WAF rule for the header: &lt;code&gt;^Basic\s+(?:\S{4})*\S{0,2}=$&lt;/code&gt;. I have not validated it.&lt;/li&gt;
&lt;li&gt;Bursts of &lt;code&gt;IllegalArgumentException&lt;/code&gt; from &lt;code&gt;java.util.Base64&lt;/code&gt; in request handlers, because every trigger throws after the write.&lt;/li&gt;
&lt;li&gt;New &lt;code&gt;hs_err_pid*.log&lt;/code&gt; files. Equixly warns the log will not name Base64, because the crash comes later when the garbage collector reads the damaged object. Endor Labs describes a SIGSEGV in a GC copy routine with a compiled &lt;code&gt;Base64$Decoder.decode0&lt;/code&gt; frame, clustered by source IP.&lt;/li&gt;
&lt;li&gt;Java processes that start a shell or open new outbound connections, which Qualys lists as a monitoring signal.
&lt;/li&gt;
&lt;/ul&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="c"&gt;# Quick sweep for recent JVM crash logs and their crash frame&lt;/span&gt;
find / -name &lt;span class="s1"&gt;'hs_err_pid*.log'&lt;/span&gt; -mtime -2 2&lt;span class="o"&gt;&amp;gt;&lt;/span&gt;/dev/null &lt;span class="o"&gt;|&lt;/span&gt; &lt;span class="k"&gt;while&lt;/span&gt; &lt;span class="nb"&gt;read&lt;/span&gt; -r f&lt;span class="o"&gt;;&lt;/span&gt; &lt;span class="k"&gt;do&lt;/span&gt;
  &lt;span class="nb"&gt;echo&lt;/span&gt; &lt;span class="s2"&gt;"$f"&lt;/span&gt;&lt;span class="o"&gt;;&lt;/span&gt; grep -m1 -E &lt;span class="s1"&gt;'^# (SIGSEGV|Problematic frame)'&lt;/span&gt; &lt;span class="s2"&gt;"$f"&lt;/span&gt;
&lt;span class="k"&gt;done&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  8. Priorities
&lt;/h2&gt;

&lt;p&gt;Qualys orders the work like this: internet-facing identity providers first, then Jira, Confluence, Jenkins and Artifactory, then other internet-facing Java services, then internal Kafka, Solr, Elasticsearch, Gerrit and Spinnaker. The first group is first because Calif's pre-auth claims name them.&lt;/p&gt;

&lt;h2&gt;
  
  
  The bottom line
&lt;/h2&gt;

&lt;p&gt;The slow part of this incident will not be the patch. It will be learning which of your processes are Java and which JDK they use. Run the inventory script once, keep its output, and you will have the answer ready for the next runtime bug too.&lt;/p&gt;

&lt;p&gt;How many of your JVMs would the script find that nobody on your team knew about?&lt;/p&gt;




&lt;p&gt;&lt;strong&gt;GDS K S&lt;/strong&gt; · &lt;a href="https://thegdsks.com" rel="noopener noreferrer"&gt;thegdsks.com&lt;/a&gt; · building &lt;a href="https://glincker.com" rel="noopener noreferrer"&gt;Glincker&lt;/a&gt; · follow on X &lt;a href="https://x.com/thegdsks" rel="noopener noreferrer"&gt;@thegdsks&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;You cannot patch a runtime you have not inventoried.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Sources: &lt;a href="https://blog.qualys.com/vulnerabilities-threat-research/2026/11/17/how-to-find-mitigate-and-patch-the-critical-java4shell-flaw-cve-2026-114938-now" rel="noopener noreferrer"&gt;Qualys&lt;/a&gt;, &lt;a href="https://www.upwind.io/blog/java4shell-what-we-know-now-and-what-comes-next" rel="noopener noreferrer"&gt;Upwind&lt;/a&gt;, &lt;a href="https://www.endorlabs.com/learn/java4shell-unauthenticated-rce-reported-in-openjdk-17-cve-2026-114938" rel="noopener noreferrer"&gt;Endor Labs&lt;/a&gt;, &lt;a href="https://equixly.com/blog/2026/11/17/cve-2026-114938-pre-auth-heap-overflow-in-java-17-21-and-25/" rel="noopener noreferrer"&gt;Equixly&lt;/a&gt;, &lt;a href="https://www.cisa.gov/news-events/alerts/2026/11/17/critical-java-vulnerability-requires-immediate-patching" rel="noopener noreferrer"&gt;CISA alert&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>java</category>
      <category>security</category>
      <category>devops</category>
      <category>kubernetes</category>
    </item>
    <item>
      <title>How to Deploy One Application to Multiple Regions With a Single Configuration (2026)</title>
      <dc:creator>Noah Grinstein</dc:creator>
      <pubDate>Wed, 18 Nov 2026 02:48:44 +0000</pubDate>
      <link>https://dev.to/noahcontrolplane/how-to-deploy-one-application-to-multiple-regions-with-a-single-configuration-2026-43hg</link>
      <guid>https://dev.to/noahcontrolplane/how-to-deploy-one-application-to-multiple-regions-with-a-single-configuration-2026-43hg</guid>
      <description>&lt;p&gt;Keep one definition of your application and a short list of per-region values, then let a tool expand that definition into every target region. Infrastructure-as-code tools apply one module or template per region. Options include Terraform with one module block per region alias, OpenTofu 1.9 or later looping a provider over a region list with &lt;code&gt;for_each&lt;/code&gt;, Terraform Stacks, Pulumi, or AWS CloudFormation StackSets. GitOps tools stamp one manifest set onto many clusters with Argo CD ApplicationSets, Flux with Kustomize overlays, or Karmada. Platforms such as Control Plane run one workload definition in every location of a group. Whichever you choose, roll changes out region by region with health checks between waves, keep state isolated per region, and solve global routing and data replication alongside the deployment.&lt;/p&gt;

&lt;p&gt;Disclosure: Control Plane publishes this guide.&lt;/p&gt;

&lt;h2&gt;
  
  
  TL;DR
&lt;/h2&gt;

&lt;p&gt;Define the app once, vary only regional values, and roll out in gated waves.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;One definition plus per-region values.&lt;/strong&gt; Store the application spec once and inject only what must differ, such as endpoints, secret values, instance types, and quotas.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Three groups of tools.&lt;/strong&gt; IaC templates applied per region, GitOps or Kubernetes tools that target many clusters, and platforms that map one workload to many locations.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;What must vary per region.&lt;/strong&gt; Database endpoints, instance types, and quota headroom, plus secret values and identities in most setups; residency policy is shared but enforced per region.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Per-region state.&lt;/strong&gt; Give each region its own state key, workspace, or stack, and store state outside the regions it manages.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Roll out in waves with health gates.&lt;/strong&gt; Start with a low-traffic canary region, then one region per continent, then the rest, with error-rate and latency gates before each wave.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Routing and data are separate problems.&lt;/strong&gt; A single config deploys the app, but you still need a global routing layer, and databases still need their own replication.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Where Control Plane fits.&lt;/strong&gt; Control Plane’s Global Virtual Cloud (GVC) runs one workload definition in every location you list across AWS, GCP, Azure, and Oracle Cloud Infrastructure (OCI).&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  How do I deploy one application to multiple regions with a single configuration?
&lt;/h2&gt;

&lt;p&gt;Write the application definition once, parameterize the few values that differ between regions, and let your tooling create a deployment per region. That removes copy-paste drift and turns adding or removing a region into a one-line change to a list.&lt;/p&gt;

&lt;p&gt;Most tools fall into three groups. IaC tools apply one module or template per region. GitOps and Kubernetes tools generate one application per cluster from one manifest set. Location-aware platforms run one workload definition wherever the platform is configured to reach. Each differs in how it orders rollouts and detects drift.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Pattern&lt;/th&gt;
&lt;th&gt;Example tools&lt;/th&gt;
&lt;th&gt;What the single config is&lt;/th&gt;
&lt;th&gt;How per-region values are supplied&lt;/th&gt;
&lt;th&gt;Rollout control&lt;/th&gt;
&lt;th&gt;Drift handling&lt;/th&gt;
&lt;th&gt;Main limit&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;IaC module applied per region&lt;/td&gt;
&lt;td&gt;Terraform (one module block per region alias) or OpenTofu 1.9+ (provider &lt;code&gt;for_each&lt;/code&gt;)&lt;/td&gt;
&lt;td&gt;A reusable module&lt;/td&gt;
&lt;td&gt;Variable maps keyed by region name&lt;/td&gt;
&lt;td&gt;CI-driven apply order&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;terraform plan&lt;/code&gt; or &lt;code&gt;tofu plan&lt;/code&gt; per region&lt;/td&gt;
&lt;td&gt;Terraform needs a module block per region alias; separate state per region is recommended&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Terraform Stacks deployments&lt;/td&gt;
&lt;td&gt;Terraform Stacks&lt;/td&gt;
&lt;td&gt;A stack definition with a deployment per region&lt;/td&gt;
&lt;td&gt;Input variables per deployment&lt;/td&gt;
&lt;td&gt;Deployment groups with auto-approve rules and failure tolerance (HCP Terraform Plus)&lt;/td&gt;
&lt;td&gt;Each deployment’s plan shows changes against live state&lt;/td&gt;
&lt;td&gt;Requires HCP Terraform or Terraform Enterprise&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Pulumi stacks per region&lt;/td&gt;
&lt;td&gt;Pulumi CLI, Pulumi Cloud&lt;/td&gt;
&lt;td&gt;A Pulumi program&lt;/td&gt;
&lt;td&gt;Stack-specific config files, or explicit regional providers in one stack&lt;/td&gt;
&lt;td&gt;Stack-by-stack updates, scriptable with the Automation API&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;pulumi refresh --preview-only&lt;/code&gt; per stack&lt;/td&gt;
&lt;td&gt;A stack per region adds stacks to manage; one stack with explicit regional providers is the alternative&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;AWS CloudFormation StackSets&lt;/td&gt;
&lt;td&gt;AWS CloudFormation&lt;/td&gt;
&lt;td&gt;A CloudFormation template&lt;/td&gt;
&lt;td&gt;Parameter overrides per account and Region&lt;/td&gt;
&lt;td&gt;Sequential or parallel Region deployment, failure tolerance, maximum concurrent accounts&lt;/td&gt;
&lt;td&gt;Drift detection on stack instances&lt;/td&gt;
&lt;td&gt;AWS only, limited to CloudFormation resource types&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Azure deployment from one template&lt;/td&gt;
&lt;td&gt;Azure Bicep, ARM templates&lt;/td&gt;
&lt;td&gt;A Bicep or ARM template&lt;/td&gt;
&lt;td&gt;Parameter files per region or subscription&lt;/td&gt;
&lt;td&gt;Pipeline stages in Azure Pipelines or GitHub Actions&lt;/td&gt;
&lt;td&gt;What-if previews changes against live resources before each deployment&lt;/td&gt;
&lt;td&gt;Azure only&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Google Cloud Deploy multi-target&lt;/td&gt;
&lt;td&gt;Google Cloud Deploy&lt;/td&gt;
&lt;td&gt;A delivery pipeline with Skaffold config&lt;/td&gt;
&lt;td&gt;Child targets with their own deploy parameters&lt;/td&gt;
&lt;td&gt;Parallel or serial promotion through targets&lt;/td&gt;
&lt;td&gt;No drift detection; verify jobs test each rollout after deploy&lt;/td&gt;
&lt;td&gt;Runs on Google Cloud and uses Skaffold; targets are GKE, Cloud Run, attached clusters, or custom types&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Helm chart with per-region values&lt;/td&gt;
&lt;td&gt;Helm&lt;/td&gt;
&lt;td&gt;A Helm chart&lt;/td&gt;
&lt;td&gt;Values files per region&lt;/td&gt;
&lt;td&gt;CI pipeline controls install order&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;helm diff&lt;/code&gt; plugin (use &lt;code&gt;--three-way-merge&lt;/code&gt; to see live drift)&lt;/td&gt;
&lt;td&gt;Needs a Kubernetes cluster per region&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Kustomize base plus overlays&lt;/td&gt;
&lt;td&gt;Kustomize&lt;/td&gt;
&lt;td&gt;A base directory of manifests&lt;/td&gt;
&lt;td&gt;Overlay directories per region&lt;/td&gt;
&lt;td&gt;Applied by CI or a GitOps controller&lt;/td&gt;
&lt;td&gt;GitOps controller reconciliation&lt;/td&gt;
&lt;td&gt;No built-in rollout ordering&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Argo CD ApplicationSets&lt;/td&gt;
&lt;td&gt;Argo CD ApplicationSet controller&lt;/td&gt;
&lt;td&gt;An ApplicationSet template&lt;/td&gt;
&lt;td&gt;List, cluster, or matrix generators&lt;/td&gt;
&lt;td&gt;RollingSync steps with maxUpdate (beta, must be enabled)&lt;/td&gt;
&lt;td&gt;Continuous reconciliation against Git&lt;/td&gt;
&lt;td&gt;Needs Argo CD on a management cluster&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Flux with Kustomizations per cluster&lt;/td&gt;
&lt;td&gt;Flux&lt;/td&gt;
&lt;td&gt;A Kustomization per cluster pointing to a shared source&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;postBuild&lt;/code&gt; variable substitution per Kustomization&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;dependsOn&lt;/code&gt; and health checks between Kustomizations&lt;/td&gt;
&lt;td&gt;Continuous reconciliation&lt;/td&gt;
&lt;td&gt;Ordering is manual through dependencies&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Karmada propagation policies&lt;/td&gt;
&lt;td&gt;Karmada&lt;/td&gt;
&lt;td&gt;Standard Kubernetes manifests&lt;/td&gt;
&lt;td&gt;OverridePolicy per cluster or region&lt;/td&gt;
&lt;td&gt;Placement and replica scheduling; no built-in wave ordering&lt;/td&gt;
&lt;td&gt;Karmada controller reconciliation&lt;/td&gt;
&lt;td&gt;Adds a federation control plane to run&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Control Plane GVC&lt;/td&gt;
&lt;td&gt;Control Plane&lt;/td&gt;
&lt;td&gt;A workload definition in a GVC&lt;/td&gt;
&lt;td&gt;Control Plane’s &lt;code&gt;spec.localOptions&lt;/code&gt; override settings in named locations&lt;/td&gt;
&lt;td&gt;Rolling updates; minReadySeconds sets how long new replicas run before the rollout continues&lt;/td&gt;
&lt;td&gt;Drift checks run in Terraform, Pulumi, or a GitOps pipeline when those manage Control Plane resources&lt;/td&gt;
&lt;td&gt;Volume data stays in each location&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Teams already deep in Terraform will find a module called once per region familiar. Teams running Kubernetes across clouds often reach for &lt;a href="https://controlplane.com/blog/post/argo-cd-vs-flux-gitops-environments-clusters?utm_source=devto&amp;amp;utm_medium=syndication&amp;amp;utm_campaign=deploy-one-app-multiple-regions-single-configuration" rel="noopener noreferrer"&gt;Argo CD ApplicationSets or Flux&lt;/a&gt;. Teams that want to stop running clusters and IaC pipelines per region can adopt a platform that maps one configuration to many locations.&lt;/p&gt;

&lt;h2&gt;
  
  
  What should stay shared and what should vary per region?
&lt;/h2&gt;

&lt;p&gt;A single configuration works only if you are strict about which values are global and which are regional. Sharing too little brings back drift, and sharing too much breaks regions with different quotas, endpoints, or compliance rules.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Setting&lt;/th&gt;
&lt;th&gt;Keep in the shared definition?&lt;/th&gt;
&lt;th&gt;Why&lt;/th&gt;
&lt;th&gt;How to supply the regional value&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Container image and version&lt;/td&gt;
&lt;td&gt;Yes&lt;/td&gt;
&lt;td&gt;One immutable artifact means every region runs the same code&lt;/td&gt;
&lt;td&gt;Tag or digest set once in the shared spec&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;App configuration (non-endpoint)&lt;/td&gt;
&lt;td&gt;Yes&lt;/td&gt;
&lt;td&gt;One config set keeps behavior the same in every region&lt;/td&gt;
&lt;td&gt;Set once in the shared spec&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Feature flags&lt;/td&gt;
&lt;td&gt;Shared flag set, regional targeting&lt;/td&gt;
&lt;td&gt;Most flags should behave the same everywhere, but some must differ for residency, legal, or regional launch reasons&lt;/td&gt;
&lt;td&gt;The flag service uses region as a targeting attribute&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Replica counts and autoscaling limits&lt;/td&gt;
&lt;td&gt;Mostly yes, override where needed&lt;/td&gt;
&lt;td&gt;Traffic differs by region&lt;/td&gt;
&lt;td&gt;Per-region variable or overlay&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Instance or node types&lt;/td&gt;
&lt;td&gt;No&lt;/td&gt;
&lt;td&gt;Not every instance family exists in every region&lt;/td&gt;
&lt;td&gt;Per-region variable or node selector&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Secrets and encryption keys&lt;/td&gt;
&lt;td&gt;Reference shared, value regional&lt;/td&gt;
&lt;td&gt;Regional copies limit blast radius, and residency rules can require them&lt;/td&gt;
&lt;td&gt;The shared spec names the secret; each region’s secrets manager supplies the value at runtime&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Database endpoints and replicas&lt;/td&gt;
&lt;td&gt;No&lt;/td&gt;
&lt;td&gt;Reads go to the local replica, and writes go to the primary unless the database supports multiple primaries&lt;/td&gt;
&lt;td&gt;Per-region environment variable or config map&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;DNS records and certificates&lt;/td&gt;
&lt;td&gt;Partly&lt;/td&gt;
&lt;td&gt;Users reach one global hostname; regional hostnames are optional and used for health checks or debugging&lt;/td&gt;
&lt;td&gt;Global record in the routing layer; regional records and certificates provisioned per region when used&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Quotas and service limits&lt;/td&gt;
&lt;td&gt;No&lt;/td&gt;
&lt;td&gt;Quotas are granted and consumed per region, so one region can run out while others have headroom&lt;/td&gt;
&lt;td&gt;Validate before deploying and request increases per region&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Data residency and allowed regions&lt;/td&gt;
&lt;td&gt;Shared as policy, enforced per region&lt;/td&gt;
&lt;td&gt;Compliance rules are global, but enforcement happens where data lands&lt;/td&gt;
&lt;td&gt;
&lt;a href="https://controlplane.com/blog/post/policy-as-code-multi-cloud-iac-governance?utm_source=devto&amp;amp;utm_medium=syndication&amp;amp;utm_campaign=deploy-one-app-multiple-regions-single-configuration" rel="noopener noreferrer"&gt;Policy-as-code&lt;/a&gt; gates in CI or admission control&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;IAM roles and identities&lt;/td&gt;
&lt;td&gt;Partly&lt;/td&gt;
&lt;td&gt;IAM is global within an AWS account or GCP project, so identities differ per account, project, or cloud&lt;/td&gt;
&lt;td&gt;Per-account role ARN, service account, or managed identity, scoped to that region’s resources&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Observability endpoints&lt;/td&gt;
&lt;td&gt;Mostly yes&lt;/td&gt;
&lt;td&gt;Central observability is the goal, but some collectors are regional&lt;/td&gt;
&lt;td&gt;Regional collector endpoint with global aggregation&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Maintenance windows&lt;/td&gt;
&lt;td&gt;No&lt;/td&gt;
&lt;td&gt;Time zones and traffic peaks differ&lt;/td&gt;
&lt;td&gt;Per-region schedule&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h3&gt;
  
  
  Keeping state per region
&lt;/h3&gt;

&lt;p&gt;Give each region its own state. When one state file covers every region, every plan and apply touches all of them, so an error or outage in one region blocks changes everywhere. Use a separate state key, workspace, or Pulumi stack per region, and store state outside the regions it manages so a regional outage does not lock you out of your recovery tooling.&lt;/p&gt;

&lt;p&gt;In Kubernetes deployments, each cluster keeps its own state, and GitOps controllers reconcile each cluster separately. One commit still reaches every cluster at once unless you configure progressive sync or dependency ordering, as covered in &lt;a href="https://controlplane.com/blog/post/long-lived-infrastructure-gitops-rolling-updates?utm_source=devto&amp;amp;utm_medium=syndication&amp;amp;utm_campaign=deploy-one-app-multiple-regions-single-configuration" rel="noopener noreferrer"&gt;long-lived infrastructure, GitOps, and rolling updates&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  How do you roll out a change across regions safely?
&lt;/h2&gt;

&lt;p&gt;Deploying to every region at once turns a small bug into a global incident, so roll out in waves with health gates between them. Stage the previous image and configuration before wave 1 starts. These waves are an example; adapt the number of waves, the regions in each, and the gates to your traffic and risk tolerance.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Wave&lt;/th&gt;
&lt;th&gt;Which regions&lt;/th&gt;
&lt;th&gt;Gate to proceed&lt;/th&gt;
&lt;th&gt;Rollback trigger&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;1: Canary&lt;/td&gt;
&lt;td&gt;One low-traffic region with the same dependencies as larger regions; avoid the region that hosts your management tooling or global config&lt;/td&gt;
&lt;td&gt;Error rate, latency, and synthetic checks hold steady through at least one daily traffic peak&lt;/td&gt;
&lt;td&gt;Error rate exceeds the baseline by a set threshold, or synthetic checks fail&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;2: One region per continent&lt;/td&gt;
&lt;td&gt;One region in each remaining continent or major geography&lt;/td&gt;
&lt;td&gt;Wave 1 gates, plus database replication lag and resource saturation within bounds&lt;/td&gt;
&lt;td&gt;Any promoted region breaches error or latency thresholds&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;3: Remaining regions&lt;/td&gt;
&lt;td&gt;All regions not yet updated&lt;/td&gt;
&lt;td&gt;All prior gates&lt;/td&gt;
&lt;td&gt;Any region fails health checks or a dependency degrades&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Post-rollout verification&lt;/td&gt;
&lt;td&gt;Every region&lt;/td&gt;
&lt;td&gt;Full synthetic test suite passes everywhere, and a configuration drift audit is clean&lt;/td&gt;
&lt;td&gt;A delayed failure traces back to the change&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h3&gt;
  
  
  Bake time
&lt;/h3&gt;

&lt;p&gt;Each wave needs a bake period during which the new version serves production traffic with no further changes. Later waves can move faster, but keep a bake period in high-traffic regions because their blast radius is largest. A rollout across many regions can take days.&lt;/p&gt;

&lt;h3&gt;
  
  
  Per-region approvals
&lt;/h3&gt;

&lt;p&gt;Pipelines can require approval between waves. AWS CodePipeline supports manual approval actions in a stage. GitHub Actions environments can require reviewers before a deployment job runs (private repositories need GitHub Enterprise). These turn your rollout waves from a process document into a constraint the system enforces.&lt;/p&gt;

&lt;h3&gt;
  
  
  Rollback
&lt;/h3&gt;

&lt;p&gt;If a failure is local to one region, roll back that region to the staged image and configuration. If it traces to the change itself, halt the rollout and roll back every region already on the new version. Use expand-and-contract database migrations so old and new versions can share the same schema during a partial rollback.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://controlplane.com/blog/post/test-failover-without-taking-production-down?utm_source=devto&amp;amp;utm_medium=syndication&amp;amp;utm_campaign=deploy-one-app-multiple-regions-single-configuration" rel="noopener noreferrer"&gt;Test failover and rollback regularly without taking production down&lt;/a&gt; so the procedures work when you need them.&lt;/p&gt;

&lt;h2&gt;
  
  
  What does a single configuration not solve?
&lt;/h2&gt;

&lt;p&gt;A single configuration puts your application in many regions, but it does not handle global routing, data replication, or regional capacity.&lt;/p&gt;

&lt;h3&gt;
  
  
  Global routing
&lt;/h3&gt;

&lt;p&gt;Users need to reach the nearest healthy region through a global load balancer, Anycast IP, or health-checked DNS. Routing policies can be latency-based, geography-based, weighted, or priority-based failover. Health checks at the routing layer must test application readiness, because a TCP check passes even when a region is running but degraded.&lt;/p&gt;

&lt;h3&gt;
  
  
  Data replication
&lt;/h3&gt;

&lt;p&gt;Your pipeline deploys the application in each region, but it does not move data between them. Each stateful service needs a replication strategy: synchronous replication for strong consistency, asynchronous replication for lower write latency, or partitioning so each record has one home region. The choice depends on your recovery point and recovery time objectives, write latency budget, and tolerance for replication lag.&lt;/p&gt;

&lt;h3&gt;
  
  
  Regional capacity
&lt;/h3&gt;

&lt;p&gt;Cloud providers do not offer the same instance types, quotas, or services in every region. A deployment that works in us-east-1 can fail in ap-southeast-3 (Jakarta), an opt-in region that must be enabled per account and offers fewer instance families. Validate capacity and request quota before each new region.&lt;/p&gt;

&lt;p&gt;Routing, replication, and capacity planning are covered in more depth in &lt;a href="https://controlplane.com/blog/post/run-app-across-multiple-regions?utm_source=devto&amp;amp;utm_medium=syndication&amp;amp;utm_campaign=deploy-one-app-multiple-regions-single-configuration" rel="noopener noreferrer"&gt;running your app across multiple regions&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  How Control Plane fits
&lt;/h2&gt;

&lt;p&gt;On Control Plane, the platform expands one workload definition into each region, so your pipeline does not loop over regions.&lt;/p&gt;

&lt;p&gt;Control Plane is the unbreakable platform for running production workloads. It runs serverless, standard, stateful, and cron workloads natively on AWS, GCP, Azure, and Oracle Cloud Infrastructure (OCI), VM workloads on locations joined through Control Plane’s Managed Kubernetes, and workloads on Kubernetes clusters you already run or your own machines, including on premises, active-active across regions and clouds.&lt;/p&gt;

&lt;p&gt;A Global Virtual Cloud (GVC) is Control Plane’s named set of locations across AWS, GCP, Azure, and OCI regions, plus your own clusters and servers. A workload runs in every location of its GVC, so one workload definition deploys to every region in the GVC. Adding or removing a region means editing the GVC’s location list.&lt;/p&gt;

&lt;p&gt;On Control Plane, a workload’s &lt;code&gt;spec.defaultOptions&lt;/code&gt; apply in every location of its GVC, and &lt;code&gt;spec.localOptions&lt;/code&gt; override settings, such as autoscaling limits or suspending the workload, in named locations. Each Control Plane workload that serves traffic gets a canonical endpoint, a hostname that uses DNS to send users to the nearest location where the workload passes its readiness probes.&lt;/p&gt;

&lt;p&gt;Control Plane handles Day 2 operations for you, including autoscaling, built-in observability, and security. Control Plane is PCI DSS Level 1, SOC 2 Type II, HIPAA, and GDPR compliant. Control Plane resources can be managed with Terraform, Pulumi, Control Plane’s cpln CLI, or GitOps pipelines.&lt;/p&gt;

&lt;p&gt;Control Plane does not replicate volume data between locations, so databases need their own replication strategy.&lt;/p&gt;

&lt;h2&gt;
  
  
  FAQ
&lt;/h2&gt;

&lt;p&gt;These answers cover Terraform, Kubernetes, secrets, state, and rollout order for multi-region deployments.&lt;/p&gt;

&lt;h3&gt;
  
  
  How do I deploy one application to multiple regions with a single configuration?
&lt;/h3&gt;

&lt;p&gt;Write the spec once, inject per-region values, and let IaC, GitOps, or a location-aware platform create each regional deployment. Then roll changes out in waves, starting with a canary region, with health gates between waves.&lt;/p&gt;

&lt;h3&gt;
  
  
  Can Terraform deploy to multiple regions at once?
&lt;/h3&gt;

&lt;p&gt;Yes. In Terraform, define one provider alias per region and call your module once per alias. OpenTofu 1.9 and later can loop a provider over a region list with &lt;code&gt;for_each&lt;/code&gt;. AWS provider v6 also lets most resources set their own &lt;code&gt;region&lt;/code&gt;, so one provider block can manage many AWS regions. Terraform Stacks, in HCP Terraform and Terraform Enterprise, let each deployment target a region with its own inputs.&lt;/p&gt;

&lt;h3&gt;
  
  
  How do I deploy to multiple regions with Kubernetes?
&lt;/h3&gt;

&lt;p&gt;Use a GitOps controller that targets many clusters. Argo CD ApplicationSets generate one Application per cluster from a template. Flux applies a Kustomization per cluster that points at a shared source with per-cluster substitutions. Karmada propagates manifests to member clusters through propagation and override policies.&lt;/p&gt;

&lt;h3&gt;
  
  
  What is an Argo CD ApplicationSet?
&lt;/h3&gt;

&lt;p&gt;An ApplicationSet is an Argo CD custom resource that generates many Application resources from one template. List generators supply explicit values, cluster generators discover registered clusters, and matrix generators combine two generators. Progressive Syncs, a beta feature you must enable, roll changes out in ordered steps and cap how many Applications update at once.&lt;/p&gt;

&lt;h3&gt;
  
  
  How do I keep secrets different per region with one configuration?
&lt;/h3&gt;

&lt;p&gt;Reference each secret by name in the shared spec and let each region’s secrets manager supply the value at runtime. If your IaC creates only the secret’s name and not its value, the value stays out of images and IaC state.&lt;/p&gt;

&lt;h3&gt;
  
  
  Should I deploy to all regions at the same time?
&lt;/h3&gt;

&lt;p&gt;No. Start with a canary region, watch it through at least one daily traffic peak, then promote in waves with automated health gates. This limits the blast radius and leaves a rollback path before the change reaches high-traffic regions.&lt;/p&gt;

&lt;h3&gt;
  
  
  How do I handle Terraform state for multiple regions?
&lt;/h3&gt;

&lt;p&gt;Give each region its own workspace or state key so each one plans and applies independently. Store the state outside the regions it manages, so an outage in one region does not block the tooling you need to recover it.&lt;/p&gt;

&lt;h3&gt;
  
  
  What is AWS CloudFormation StackSets?
&lt;/h3&gt;

&lt;p&gt;CloudFormation StackSets let you deploy one CloudFormation template across multiple AWS accounts and Regions from a single administrator account. You can override parameters per account and Region, choose sequential or parallel Region deployment, and set failure tolerance and concurrency.&lt;/p&gt;

&lt;h3&gt;
  
  
  How does Control Plane deploy one workload to many regions?
&lt;/h3&gt;

&lt;p&gt;Control Plane runs one workload definition in every location of a Global Virtual Cloud (GVC), which can include AWS, GCP, Azure, and OCI regions, your own clusters, and your own machines, including on premises. Baseline settings apply everywhere, and per-location overrides change settings such as autoscaling limits in named locations. To add a region, add it to the GVC.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://controlplane.com/requestdemo?utm_source=devto&amp;amp;utm_medium=syndication&amp;amp;utm_campaign=deploy-one-app-multiple-regions-single-configuration" rel="noopener noreferrer"&gt;Talk to the Control Plane team&lt;/a&gt; or &lt;a href="https://console.cpln.io/signup" rel="noopener noreferrer"&gt;sign up free&lt;/a&gt;.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Originally published on the &lt;a href="https://controlplane.com/blog/post/deploy-one-app-multiple-regions-single-configuration?utm_source=devto&amp;amp;utm_medium=syndication&amp;amp;utm_campaign=deploy-one-app-multiple-regions-single-configuration" rel="noopener noreferrer"&gt;Control Plane blog&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>cloud</category>
      <category>devops</category>
      <category>kubernetes</category>
      <category>sre</category>
    </item>
    <item>
      <title>Affordable Kubernetes: The best options</title>
      <dc:creator>Boluwatife Morawo</dc:creator>
      <pubDate>Wed, 18 Nov 2026 02:27:20 +0000</pubDate>
      <link>https://dev.to/hayone1/affordable-kubernetes-the-best-options-3d3n</link>
      <guid>https://dev.to/hayone1/affordable-kubernetes-the-best-options-3d3n</guid>
      <description>&lt;p&gt;Kubernetes brought democracy to the cloud somewhat. Anyone in the community can suggest a feature by writing a &lt;a href="https://www.kubernetes.dev/resources/keps/" rel="noopener noreferrer"&gt;Kubernetes Enhancement Proposal (KEP)&lt;/a&gt;. You can deploy a cluster on several clouds and choose how agnostic or locked-in you become.&lt;br&gt;
That's great, but it's still the cloud, and the cloud is still expensive. This may be discouraging to someone who's trying to learn Kubernetes for real, or a startup that just wants an affordable test environment. The good news is that there are several affordable options to stand up a functional and secure k8s cluster.&lt;/p&gt;
&lt;h2&gt;
  
  
  What are your options?
&lt;/h2&gt;

&lt;p&gt;&lt;/p&gt;
  TL;DR
  &lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;&lt;/th&gt;
&lt;th&gt;&lt;a href="https://www.aliexpress.com/item/1005006801741948.html" rel="noopener noreferrer"&gt;OrangePi 5 Pro&lt;/a&gt;&lt;/th&gt;
&lt;th&gt;&lt;a href="https://www.hetzner.com/cloud/regular-performance/" rel="noopener noreferrer"&gt;Hetzner&lt;/a&gt;&lt;/th&gt;
&lt;th&gt;&lt;a href="https://contabo.com/en/vps-performance/" rel="noopener noreferrer"&gt;Contabo&lt;/a&gt;&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Setup Difficulty&lt;/td&gt;
&lt;td&gt;⬤ ⬤ ⬤ ⬤&lt;/td&gt;
&lt;td&gt;⬤ ⬤&lt;/td&gt;
&lt;td&gt;⬤ ⬤ ⬤&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Cost (test env)&lt;/td&gt;
&lt;td&gt;$350 for 16GB RAM, 8 CPU&lt;br&gt;(one time purchase)&lt;/td&gt;
&lt;td&gt;$80 for 16GB RAM, 8 CPU&lt;br&gt;(postpaid monthly)&lt;/td&gt;
&lt;td&gt;$45 for 24GB RAM, 8 CPU&lt;br&gt;(prepaid monthly)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Best for&lt;/td&gt;
&lt;td&gt;labs, test env&lt;/td&gt;
&lt;td&gt;labs, test-prod env&lt;/td&gt;
&lt;td&gt;labs, test-prod env&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;



&lt;p&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fi3z9p7mtwyvmjvdn6gea.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fi3z9p7mtwyvmjvdn6gea.png" alt="Line chart of total cost over 12 months for a 16GB, 8 CPU test environment. The OrangePi stays flat at $350 after the one-time purchase. Hetzner grows by $80 a month and passes the OrangePi in month 5. Contabo grows by $45 a month and passes the OrangePi in month 8." width="799" height="413"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Firstly, it's important to remove any stereotypes that tell you that production environments can only be deployed on a major hyperscaler or some super expensive self-maintained data center. There are several organizations that were able to reduce their entire cloud bill from tens of thousands to a few thousand dollars because they changed their mindset. That said, let's get into the options.&lt;/p&gt;

&lt;h2&gt;
  
  
  OrangePi
&lt;/h2&gt;

&lt;p&gt;This is one of the more powerful cousins of the Raspberry Pi, with a lot more options. It has the most expensive initial cost among the options. For about $350 you can get a board with 8 CPUs and 16GB RAM like the &lt;a href="https://www.aliexpress.com/item/1005006801741948.html" rel="noopener noreferrer"&gt;Orange Pi 5 Pro&lt;/a&gt;, &lt;a href="https://www.aliexpress.com/item/1005007356107781.html" rel="noopener noreferrer"&gt;Orange Pi 5 Max&lt;/a&gt; and &lt;a href="https://www.aliexpress.com/item/1005010157378785.html" rel="noopener noreferrer"&gt;Orange Pi 6 Plus&lt;/a&gt;. If you have a higher budget, you could also get 32GB variants like this &lt;a href="https://www.aliexpress.com/item/1005012530475330.html" rel="noopener noreferrer"&gt;Orange Pi 6 Plus&lt;/a&gt;.&lt;br&gt;
You'd also need to get a router, network cable, power cable and charging brick that meets the power demand of the unit you have.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;⚡ Meeting the power requirement is very essential, or your unit just won't run.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h3&gt;
  
  
  My OrangePi Setup
&lt;/h3&gt;

&lt;p&gt;I use my OrangePi cluster to test fairly heavy workloads like the &lt;a href="https://grafana.com/about/grafana-stack/" rel="noopener noreferrer"&gt;LGTM+ stack&lt;/a&gt; running in microservices mode. This setup should give an idea of a practical configuration, although the final price you get might vary.&lt;/p&gt;

&lt;h4&gt;
  
  
  Physical Components
&lt;/h4&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Item&lt;/th&gt;
&lt;th&gt;QTY&lt;/th&gt;
&lt;th&gt;Total Price&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;a href="https://www.aliexpress.com/item/1005006800863351.html" rel="noopener noreferrer"&gt;Orange Pi 5 Pro (8 CPU, 16GB RAM)&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;x4&lt;/td&gt;
&lt;td&gt;$1,264.33&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;a href="https://www.aliexpress.com/item/1005006160291558.html" rel="noopener noreferrer"&gt;M2.5 Series Hex Brass Column&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;x1&lt;/td&gt;
&lt;td&gt;$11.73&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;a href="https://www.aliexpress.com/item/1005007294796796.html" rel="noopener noreferrer"&gt;Wire Zip Ties&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;x1&lt;/td&gt;
&lt;td&gt;$1.32&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;a href="https://www.aliexpress.com/item/1005013515583073.html" rel="noopener noreferrer"&gt;SanDisk Extreme Pro Micro SD&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;x4&lt;/td&gt;
&lt;td&gt;$63.84&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;a href="https://www.aliexpress.com/item/1005004405900182.html" rel="noopener noreferrer"&gt;KingSpec SSD (128GB)&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;x4&lt;/td&gt;
&lt;td&gt;$129.81&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;a href="https://www.aliexpress.com/item/1005006989183547.html" rel="noopener noreferrer"&gt;Orange Pi 5 Pro Acrylic Case&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;x4&lt;/td&gt;
&lt;td&gt;$27.17&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;a href="https://www.aliexpress.com/item/1005010379307213.html" rel="noopener noreferrer"&gt;Orange Pi 5 Pro Copper Case&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;x4&lt;/td&gt;
&lt;td&gt;$89.05&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;a href="https://www.aliexpress.com/item/1005008525558891.html" rel="noopener noreferrer"&gt;Cooling Fan 30 x 30 x 7mm (5V)&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;x4&lt;/td&gt;
&lt;td&gt;$11.96&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;a href="https://www.aliexpress.com/item/1005008830706618.html" rel="noopener noreferrer"&gt;8-Port Ethernet Network Switch&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;x1&lt;/td&gt;
&lt;td&gt;$20.96&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Broadband router (already had one)&lt;/td&gt;
&lt;td&gt;x1&lt;/td&gt;
&lt;td&gt;-&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Total Price&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;$1,620.17&lt;/strong&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;I had also bought a &lt;a href="https://www.aliexpress.com/item/1005004910531555.html" rel="noopener noreferrer"&gt;10 Ports USB 3.0 HUB Charging&lt;/a&gt; at some point. I paused using it for several months, but when I finally decided to use it again, it didn't work.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;💡 If an item is no longer available from the linked seller, it can probably be bought from another seller.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h4&gt;
  
  
  Pi K8s Setup
&lt;/h4&gt;

&lt;p&gt;I installed &lt;a href="https://github.com/mack42/OrangePi5Pro" rel="noopener noreferrer"&gt;Ubuntu 26.04&lt;/a&gt; on each server, initially on the SD cards, then on the SSD drives. The easier option is to install the OS only on the SD card, as it allows you to use the SSD fully for persistent volume storage.&lt;/p&gt;

&lt;p&gt;I installed k3s using a modified version of the &lt;a href="https://github.com/k3s-io/k3s-ansible" rel="noopener noreferrer"&gt;k3s-ansible&lt;/a&gt; project. I also used Cilium for the CNI, load balancer and Gateway API, but you'd be fine using the defaults.&lt;/p&gt;

&lt;p&gt;I installed external-dns + cert-manager and integrated them with Azure DNS (I bought the domain from Hostinger and &lt;a href="https://learn.microsoft.com/en-us/azure/dns/dns-delegate-domain-azure-dns" rel="noopener noreferrer"&gt;delegated it to Azure&lt;/a&gt;). At this point, I could only access the cluster when on the local network, but I didn't have to deal with certificate issues or mess with host entries.&lt;/p&gt;

&lt;p&gt;For access over the internet, I bought a cheap VPS on Contabo, linked it to the Pi servers using &lt;a href="https://pinggy.io/blog/ssh_reverse_tunnelling/" rel="noopener noreferrer"&gt;SSH reverse tunneling&lt;/a&gt; and exposed it via TLSRoute (k3s was also installed on the Contabo server).&lt;/p&gt;

&lt;p&gt;That method wasn't really neat, so what I'd rather advise is to use &lt;a href="https://github.com/fatedier/frp" rel="noopener noreferrer"&gt;fast reverse proxy&lt;/a&gt;, which will link the 2 clusters (the Pi cluster and the one on the server).&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Tailscale can also do the job.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fzu38aup082oysrlxihqc.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fzu38aup082oysrlxihqc.png" alt="How a reader reaches the OrangePi cluster: the browser connects to a public Contabo VPS running k3s, and an frp tunnel (or SSH reverse tunnel, or Tailscale) carries the traffic through the home router and switch to the four Orange Pi nodes. On the local network, devices reach the nodes directly." width="799" height="589"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Hetzner
&lt;/h2&gt;

&lt;p&gt;Hetzner is the most mature and production-ready option, thanks to community contributions. One regular performance server with 8 vCPU and 16GB RAM - &lt;a href="https://www.hetzner.com/cloud/regular-performance/" rel="noopener noreferrer"&gt;CPX42&lt;/a&gt; will cost ~$80.&lt;/p&gt;

&lt;h3&gt;
  
  
  My Hetzner Setup
&lt;/h3&gt;

&lt;p&gt;I mostly use Hetzner for short end-to-end tests when I need a throwaway server. Though you can buy domains from Hetzner's &lt;a href="https://www.hetzner.com/registrationrobot/" rel="noopener noreferrer"&gt;domain registration robot&lt;/a&gt;, I still bought my domain from Hostinger and delegated it to Hetzner's nameservers.&lt;/p&gt;

&lt;p&gt;I use the &lt;a href="https://github.com/hcloud-k8s/terraform-hcloud-kubernetes" rel="noopener noreferrer"&gt;hcloud-k8s&lt;/a&gt; Terraform module to set up the cluster, but you can also use &lt;a href="https://github.com/vitobotta/hetzner-k3s" rel="noopener noreferrer"&gt;hetzner-k3s&lt;/a&gt;. A good note for secure access here is that it comes with Tailscale support.&lt;/p&gt;

&lt;h2&gt;
  
  
  Contabo
&lt;/h2&gt;

&lt;p&gt;Contabo is a really great option once you understand its quirks. For example, payment is prepaid, so you can't just spin up and tear down servers as you wish. You can cancel a server's subscription, but it will stay active till the end of its billing period since you already paid in full. Similar to Hetzner, there are also 3 main pricing tiers. The &lt;a href="https://contabo.com/en/vps/" rel="noopener noreferrer"&gt;Core VPS&lt;/a&gt; is subject to heavy sharing on CPU cores, disk I/O and network links. &lt;a href="https://contabo.com/en/vps-performance/" rel="noopener noreferrer"&gt;Performance VPS&lt;/a&gt; works similarly but uses newer AMD EPYC processors. &lt;a href="https://contabo.com/en/vps-dedicated/" rel="noopener noreferrer"&gt;Max Performance VPS (VDS)&lt;/a&gt; offers full compute isolation and is what you'll want to use for production.&lt;/p&gt;

&lt;p&gt;Contabo doesn't have feature parity with Hetzner, but it has all the features you need to create a cluster.&lt;/p&gt;

&lt;h3&gt;
  
  
  My Contabo Setup
&lt;/h3&gt;

&lt;p&gt;I personally use Contabo in production. Like Hetzner, you can &lt;a href="https://contabo.com/en/domains/" rel="noopener noreferrer"&gt;buy domains from Contabo&lt;/a&gt;, but I prefer to buy mine from Hostinger and delegate it to Contabo's nameservers. Why? Because that's the cheaper option.&lt;/p&gt;

&lt;p&gt;The Terraform module I use is &lt;a href="https://registry.terraform.io/modules/hayone1/kubernetes/contabo/latest" rel="noopener noreferrer"&gt;contabo-kubernetes&lt;/a&gt;. It's the only module available. It also comes with support for Tailscale/Headscale integration. One major difference in the architecture compared to the Hetzner setup is that your load balancer will essentially be one or more of the nodes rather than a dedicated cloud load balancer service.&lt;br&gt;
You can also use &lt;a href="https://github.com/k3s-io/k3s-ansible" rel="noopener noreferrer"&gt;k3s-ansible&lt;/a&gt; if Ansible is your preferred route.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Ff53t9fpmgcosw38cokf3.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Ff53t9fpmgcosw38cokf3.png" alt="Load balancing on Hetzner and on Contabo. On Hetzner, traffic from the internet reaches a managed Hetzner Load Balancer, which spreads it over the cluster nodes. On Contabo, traffic reaches the public IP of one or more cluster nodes, and that node acts as the load balancer for the rest of the cluster." width="800" height="390"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Wrapping up
&lt;/h2&gt;

&lt;p&gt;When you cut out most of the marketing noise, you'd find that there are several cost-effective ways to do many things, including deploying Kubernetes. What about stateful workloads like databases, you say? We'll explore that in another article, which I'll link here once it's ready.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Originally published at &lt;a href="https://codejourney.io/blog/affordable-kubernetes-the-best-options" rel="noopener noreferrer"&gt;codejourney.io&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>kubernetes</category>
      <category>devops</category>
      <category>terraform</category>
      <category>linux</category>
    </item>
    <item>
      <title>Kerentanan Kritis Kubernetes: Patch Segera untuk Keamanan Klaster</title>
      <dc:creator>IbraMedia</dc:creator>
      <pubDate>Wed, 18 Nov 2026 02:04:46 +0000</pubDate>
      <link>https://dev.to/ibramedia/kerentanan-kritis-kubernetes-patch-segera-untuk-keamanan-klaster-112l</link>
      <guid>https://dev.to/ibramedia/kerentanan-kritis-kubernetes-patch-segera-untuk-keamanan-klaster-112l</guid>
      <description>&lt;h2&gt;
  
  
  Apa Itu Kerentanan Kritis Kubernetes?
&lt;/h2&gt;

&lt;p&gt;Kubernetes, sebagai orkestrator kontainer terkemuka, menjadi tulang punggung infrastruktur cloud-native bagi jutaan organisasi di seluruh dunia. Namun, ekosistem yang kompleks ini tidak luput dari ancaman keamanan. Baru-baru ini, serangkaian kerentanan keamanan kritis telah ditemukan dalam Kubernetes, yang berpotensi membahayakan integritas dan ketersediaan klaster secara luas. Pengumuman mengenai kerentanan ini, yang dirilis pada awal Agustus 2024, menyoroti celah serius yang memerlukan perhatian dan tindakan segera dari para administrator sistem dan tim keamanan.&lt;/p&gt;

&lt;p&gt;Kerentanan ini, yang detail teknisnya sedang dianalisis secara mendalam, memungkinkan penyerang untuk mengeksploitasi kelemahan dalam komponen inti Kubernetes. Eksploitasi yang berhasil dapat berujung pada akses tidak sah, eskalasi hak istimewa, atau bahkan kendali penuh atas klaster, yang pada gilirannya dapat mengganggu layanan, mencuri data sensitif, atau menyebarkan &lt;em&gt;malware&lt;/em&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Dampak Luas pada Penyebaran Kubernetes
&lt;/h2&gt;

&lt;p&gt;Skala penyebaran Kubernetes yang masif berarti potensi dampak dari kerentanan ini sangat luas. Jutaan klaster di seluruh dunia, mulai dari penyebaran kecil hingga infrastruktur perusahaan berskala besar, berisiko tinggi. Organisasi yang mengandalkan Kubernetes untuk menjalankan aplikasi dan layanan mereka harus segera bertindak untuk menilai eksposur mereka dan menerapkan langkah-langkah mitigasi.&lt;/p&gt;

&lt;h3&gt;
  
  
  Risiko Eksploitasi dan Ancaman
&lt;/h3&gt;

&lt;p&gt;Periode risiko eksploitasi dimulai sejak penemuan kerentanan hingga klaster berhasil ditambal. Selama waktu ini, klaster yang tidak terlindungi menjadi target empuk bagi aktor jahat. Kegagalan untuk menambal kerentanan ini dengan cepat dapat mengakibatkan pelanggaran keamanan yang signifikan, kehilangan data yang tidak dapat diperbaiki, dan gangguan layanan yang berkepanjangan. Penting bagi organisasi untuk memiliki &lt;a href="https://dev.to/artikel/cara-mengamankan-klaster-kubernetes"&gt;strategi keamanan klaster Kubernetes&lt;/a&gt; yang proaktif untuk menghadapi ancaman semacam ini.&lt;/p&gt;

&lt;h2&gt;
  
  
  Versi Kubernetes yang Terpengaruh dan Cara Memeriksa
&lt;/h2&gt;

&lt;p&gt;Komunitas Kubernetes dan Cloud Native Computing Foundation (CNCF) telah merilis advisori keamanan yang merinci versi spesifik Kubernetes yang terpengaruh oleh kerentanan ini. Meskipun detail spesifik versi terus diperbarui, umumnya versi-versi yang lebih lama dan tidak mendapatkan pembaruan rutin adalah yang paling rentan. Pengguna disarankan untuk merujuk langsung ke pengumuman resmi dari blog Kubernetes dan CNCF untuk daftar lengkap versi yang terpengaruh.&lt;/p&gt;

&lt;p&gt;Untuk memeriksa apakah klaster Kubernetes Anda terpengaruh, administrator sistem harus:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Mengidentifikasi versi Kubernetes yang sedang berjalan di setiap klaster.&lt;/li&gt;
&lt;li&gt;Membandingkan versi tersebut dengan daftar yang disebutkan dalam advisori keamanan resmi.&lt;/li&gt;
&lt;li&gt;Menggunakan alat pemindaian keamanan atau perintah CLI Kubernetes untuk mengevaluasi konfigurasi dan potensi kerentanan.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Langkah-langkah Patching Mendesak
&lt;/h2&gt;

&lt;p&gt;Penambalan segera adalah langkah paling krusial untuk mitigasi risiko. Rekomendasi penambalan diberikan segera setelah pengumuman kerentanan, menekankan urgensi tindakan. Penundaan dalam menerapkan &lt;em&gt;patch&lt;/em&gt; dapat meningkatkan jendela peluang bagi penyerang.&lt;/p&gt;

&lt;h3&gt;
  
  
  Proses Pembaruan Aman
&lt;/h3&gt;

&lt;p&gt;Menerapkan &lt;em&gt;patch&lt;/em&gt; keamanan di lingkungan produksi memerlukan perencanaan yang cermat untuk menghindari gangguan layanan. Proses pembaruan yang aman biasanya melibatkan:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Membaca advisori keamanan secara menyeluruh untuk memahami dampak dan langkah-langkah spesifik.&lt;/li&gt;
&lt;li&gt;Melakukan &lt;em&gt;backup&lt;/em&gt; konfigurasi klaster dan data penting.&lt;/li&gt;
&lt;li&gt;Menguji &lt;em&gt;patch&lt;/em&gt; di lingkungan non-produksi terlebih dahulu.&lt;/li&gt;
&lt;li&gt;Menerapkan &lt;em&gt;patch&lt;/em&gt; secara bertahap, mungkin menggunakan strategi &lt;em&gt;rolling update&lt;/em&gt; atau &lt;em&gt;canary deployment&lt;/em&gt;.&lt;/li&gt;
&lt;li&gt;Memantau klaster dengan cermat setelah pembaruan untuk memastikan stabilitas dan fungsionalitas. 
Untuk panduan lebih lanjut mengenai proses ini, referensi pada &lt;a href="https://dev.to/artikel/panduan-pembaruan-kubernetes"&gt;panduan pembaruan Kubernetes&lt;/a&gt; yang aman sangat dianjurkan.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Mitigasi Jangka Panjang dan Praktik Terbaik
&lt;/h2&gt;

&lt;p&gt;Penemuan kerentanan kritis ini menyoroti tantangan berkelanjutan dalam mengamankan infrastruktur cloud-native yang kompleks. Selain penambalan segera, organisasi harus mengadopsi strategi keamanan jangka panjang yang komprehensif. Ini termasuk:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;  &lt;strong&gt;Pembaruan Rutin:&lt;/strong&gt; Pastikan semua komponen Kubernetes dan dependensinya selalu diperbarui ke versi terbaru.&lt;/li&gt;
&lt;li&gt;  &lt;strong&gt;Prinsip Hak Istimewa Terkecil:&lt;/strong&gt; Terapkan prinsip hak istimewa terkecil (&lt;em&gt;least privilege&lt;/em&gt;) untuk semua pengguna dan komponen klaster.&lt;/li&gt;
&lt;li&gt;  &lt;strong&gt;Segmentasi Jaringan:&lt;/strong&gt; Segmentasikan jaringan klaster untuk membatasi pergerakan lateral penyerang.&lt;/li&gt;
&lt;li&gt;  &lt;strong&gt;Pemantauan Keamanan:&lt;/strong&gt; Implementasikan alat pemantauan keamanan yang kuat untuk mendeteksi anomali dan aktivitas mencurigakan.&lt;/li&gt;
&lt;li&gt;  &lt;strong&gt;Manajemen Konfigurasi:&lt;/strong&gt; Tinjau dan perketat konfigurasi keamanan klaster secara teratur. Dalam konteks DevOps, penggunaan &lt;a href="https://dev.to/artikel/apa-itu-platform-engineering"&gt;Platform Engineering&lt;/a&gt; dapat sangat membantu dalam mengelola konfigurasi dan memastikan kepatuhan keamanan secara konsisten.&lt;/li&gt;
&lt;li&gt;  &lt;strong&gt;Edukasi Tim:&lt;/strong&gt; Pastikan tim keamanan dan pengembang memiliki pemahaman yang mendalam tentang praktik keamanan Kubernetes.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Kesimpulan
&lt;/h2&gt;

&lt;p&gt;Kerentanan keamanan kritis baru di Kubernetes adalah pengingat tegas akan pentingnya kewaspadaan dan tindakan proaktif dalam mengelola infrastruktur cloud-native. Dengan jutaan penyebaran yang berpotensi terpengaruh, penambalan segera bukan hanya rekomendasi, tetapi keharusan. Organisasi yang gagal bertindak cepat berisiko mengalami pelanggaran keamanan yang parah, yang dapat berdampak pada reputasi, keuangan, dan operasional. Prioritaskan pembaruan, tinjau lingkungan Anda, dan perkuat postur keamanan Kubernetes Anda untuk melindungi aset digital Anda dari ancaman yang terus berkembang.&lt;/p&gt;




&lt;p&gt;&lt;strong&gt;Topics &amp;amp; Discussion:&lt;/strong&gt;&lt;/p&gt;

&lt;h1&gt;
  
  
  kubernetes #cloud #devops #docker #aws #linux #automation
&lt;/h1&gt;

</description>
      <category>kubernetes</category>
      <category>cloud</category>
      <category>devops</category>
      <category>docker</category>
    </item>
    <item>
      <title>The Best Container Management and Networking Tools (2026): Where to Find Them, Tools by Layer, and How to Pick by Scale</title>
      <dc:creator>Noah Grinstein</dc:creator>
      <pubDate>Tue, 17 Nov 2026 22:58:16 +0000</pubDate>
      <link>https://dev.to/noahcontrolplane/the-best-container-management-and-networking-tools-2026-where-to-find-them-tools-by-layer-and-439c</link>
      <guid>https://dev.to/noahcontrolplane/the-best-container-management-and-networking-tools-2026-where-to-find-them-tools-by-layer-and-439c</guid>
      <description>&lt;p&gt;The best container management and networking tools are cataloged in the &lt;a href="https://landscape.cncf.io/" rel="noopener noreferrer"&gt;CNCF Landscape&lt;/a&gt; and &lt;a href="https://artifacthub.io/" rel="noopener noreferrer"&gt;Artifact Hub&lt;/a&gt;. The most widely used are Kubernetes or a managed Kubernetes service for orchestration, Rancher or OpenShift for multi-cluster management, Cilium or Calico for container networking and network policy, Istio or Linkerd for service mesh, and a Gateway API implementation such as Envoy Gateway or Contour for ingress. The right combination depends on scale. A single host needs Docker or Podman with a management UI, and many clusters across clouds need a fleet manager and a networking layer that spans clusters.&lt;/p&gt;

&lt;p&gt;Disclosure: Control Plane publishes this guide.&lt;/p&gt;

&lt;h2&gt;
  
  
  TL;DR
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Start at the CNCF Landscape and Artifact Hub.&lt;/strong&gt; Both are vendor-neutral catalogs of cloud-native projects, filterable by category and maturity.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Orchestration.&lt;/strong&gt; Kubernetes is the default for production. Managed Kubernetes (EKS, GKE, AKS) takes over control plane operations. Nomad handles mixed container and non-container workloads.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Multi-cluster management.&lt;/strong&gt; SUSE Rancher and Red Hat OpenShift manage fleets of clusters. Portainer covers smaller Docker, Podman, and Kubernetes environments with a visual UI.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;CNI and network policy.&lt;/strong&gt; Cilium and Calico are the most widely used open-source CNI plugins for network policy. Both enforce network policy, and both offer an eBPF dataplane.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Service mesh and Gateway API.&lt;/strong&gt; Istio and Linkerd handle mTLS, retries, and traffic management. Gateway API is the successor to Ingress, with conformant implementations that include Envoy Gateway, Istio, Cilium, Contour, Traefik, Kong, and NGINX Gateway Fabric.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Pick by scale.&lt;/strong&gt; A home lab needs Docker Compose or Podman. A single production cluster needs managed Kubernetes with Cilium or Calico. Clusters across clouds need a fleet manager plus Cilium Cluster Mesh or Submariner.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Where Control Plane fits.&lt;/strong&gt; Control Plane runs production workloads in one region or across regions and clouds with no cluster to operate, and handles orchestration, networking, and Day 2 operations, including autoscaling, observability, and security.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Where can I find the best in class container management and networking tools?
&lt;/h2&gt;

&lt;p&gt;Start with the CNCF Landscape, which maps cloud-native projects and products into categories such as container runtime, orchestration, service mesh, and observability. Each project card shows its license, CNCF maturity level (sandbox, incubating, or graduated), and repository. Artifact Hub indexes Helm charts, policies, and other packages that extend those projects.&lt;/p&gt;

&lt;p&gt;CNCF graduation is a strong maturity signal. A graduated project has passed a third-party security audit, shown broad adoption, and committed to open governance. Kubernetes, containerd, Envoy, Cilium, Istio, Linkerd, and CoreDNS are graduated. Incubating projects run in production at many organizations but have not completed graduation, and sandbox projects are earlier still.&lt;/p&gt;

&lt;p&gt;Analyst firms such as Gartner publish container management market guides, and review sites such as G2 aggregate user ratings. These are useful secondary sources, but they trail open-source releases. Project repositories, release notes, and community channels are the fastest way to check current capabilities.&lt;/p&gt;

&lt;h2&gt;
  
  
  Which tools cover each container layer?
&lt;/h2&gt;

&lt;p&gt;Most tools cover one or two layers of the stack.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Tool&lt;/th&gt;
&lt;th&gt;Layer&lt;/th&gt;
&lt;th&gt;What it manages&lt;/th&gt;
&lt;th&gt;License&lt;/th&gt;
&lt;th&gt;CNCF status&lt;/th&gt;
&lt;th&gt;Best fit&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Docker Engine and Docker Compose&lt;/td&gt;
&lt;td&gt;Container runtime and local orchestration&lt;/td&gt;
&lt;td&gt;Building, running, and composing containers on a single host (multi-host requires Swarm mode)&lt;/td&gt;
&lt;td&gt;Apache 2.0 (Engine and Compose)&lt;/td&gt;
&lt;td&gt;Not CNCF&lt;/td&gt;
&lt;td&gt;Single host, dev environments, small Compose stacks&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Podman&lt;/td&gt;
&lt;td&gt;Container runtime&lt;/td&gt;
&lt;td&gt;Running containers and pods without a daemon, with first-class rootless mode&lt;/td&gt;
&lt;td&gt;Apache 2.0&lt;/td&gt;
&lt;td&gt;Sandbox (as Podman Container Tools)&lt;/td&gt;
&lt;td&gt;Single host, security-sensitive environments&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Kubernetes&lt;/td&gt;
&lt;td&gt;Orchestration&lt;/td&gt;
&lt;td&gt;Scheduling, scaling, self-healing, and lifecycle of containerized workloads across nodes&lt;/td&gt;
&lt;td&gt;Apache 2.0&lt;/td&gt;
&lt;td&gt;Graduated&lt;/td&gt;
&lt;td&gt;One or more production clusters&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Amazon EKS, Google GKE, Azure AKS&lt;/td&gt;
&lt;td&gt;Managed orchestration&lt;/td&gt;
&lt;td&gt;Kubernetes control plane, node provisioning, upgrades&lt;/td&gt;
&lt;td&gt;Proprietary (service)&lt;/td&gt;
&lt;td&gt;Not applicable&lt;/td&gt;
&lt;td&gt;Teams wanting Kubernetes without running its control plane&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;HashiCorp Nomad&lt;/td&gt;
&lt;td&gt;Orchestration&lt;/td&gt;
&lt;td&gt;Scheduling containers, VMs, binaries, and batch jobs&lt;/td&gt;
&lt;td&gt;Business Source License 1.1&lt;/td&gt;
&lt;td&gt;Not CNCF&lt;/td&gt;
&lt;td&gt;Mixed workloads, organizations already using HashiCorp tools&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Portainer&lt;/td&gt;
&lt;td&gt;Management UI&lt;/td&gt;
&lt;td&gt;Visual management of Docker, Swarm, Podman, and Kubernetes environments&lt;/td&gt;
&lt;td&gt;Zlib (Community Edition)&lt;/td&gt;
&lt;td&gt;Not CNCF&lt;/td&gt;
&lt;td&gt;Small teams, home labs, visual management&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;SUSE Rancher&lt;/td&gt;
&lt;td&gt;Multi-cluster management&lt;/td&gt;
&lt;td&gt;Cluster provisioning, access control, policy, and monitoring across many Kubernetes clusters, with Fleet for GitOps&lt;/td&gt;
&lt;td&gt;Apache 2.0&lt;/td&gt;
&lt;td&gt;Not CNCF&lt;/td&gt;
&lt;td&gt;Multi-cluster Kubernetes fleets&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Red Hat OpenShift&lt;/td&gt;
&lt;td&gt;Enterprise Kubernetes platform&lt;/td&gt;
&lt;td&gt;Kubernetes plus CI/CD, security policies, and a developer console; fleet management through Red Hat Advanced Cluster Management&lt;/td&gt;
&lt;td&gt;OKD is Apache 2.0; OpenShift is a subscription product&lt;/td&gt;
&lt;td&gt;Not CNCF&lt;/td&gt;
&lt;td&gt;Large enterprises needing integrated governance and support&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Cilium&lt;/td&gt;
&lt;td&gt;CNI and network policy&lt;/td&gt;
&lt;td&gt;Pod networking, network policy, load balancing, and optional Hubble observability using eBPF&lt;/td&gt;
&lt;td&gt;Apache 2.0&lt;/td&gt;
&lt;td&gt;Graduated&lt;/td&gt;
&lt;td&gt;Production clusters needing eBPF networking and flow observability&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Calico&lt;/td&gt;
&lt;td&gt;CNI and network policy&lt;/td&gt;
&lt;td&gt;Pod networking, network policy, and routing with an iptables, nftables, or eBPF dataplane&lt;/td&gt;
&lt;td&gt;Apache 2.0&lt;/td&gt;
&lt;td&gt;Not CNCF&lt;/td&gt;
&lt;td&gt;Production clusters standardized on Calico’s policy model&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Flannel&lt;/td&gt;
&lt;td&gt;CNI&lt;/td&gt;
&lt;td&gt;Simple overlay pod networking&lt;/td&gt;
&lt;td&gt;Apache 2.0&lt;/td&gt;
&lt;td&gt;Not CNCF&lt;/td&gt;
&lt;td&gt;Simple clusters; default CNI in K3s&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Istio&lt;/td&gt;
&lt;td&gt;Service mesh&lt;/td&gt;
&lt;td&gt;mTLS, traffic management, retries, observability, and policy between services, in sidecar or ambient mode&lt;/td&gt;
&lt;td&gt;Apache 2.0&lt;/td&gt;
&lt;td&gt;Graduated&lt;/td&gt;
&lt;td&gt;Clusters needing application-layer security and traffic control&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Linkerd&lt;/td&gt;
&lt;td&gt;Service mesh&lt;/td&gt;
&lt;td&gt;mTLS, retries, and observability with lightweight Rust proxies&lt;/td&gt;
&lt;td&gt;Apache 2.0 (open-source edge releases; stable builds via vendors such as Buoyant)&lt;/td&gt;
&lt;td&gt;Graduated&lt;/td&gt;
&lt;td&gt;Teams wanting a lightweight service mesh&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Envoy Gateway&lt;/td&gt;
&lt;td&gt;Ingress and Gateway API&lt;/td&gt;
&lt;td&gt;North-south traffic routing using the Kubernetes Gateway API&lt;/td&gt;
&lt;td&gt;Apache 2.0&lt;/td&gt;
&lt;td&gt;Part of the Envoy project (Graduated)&lt;/td&gt;
&lt;td&gt;Clusters adopting Gateway API&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;CoreDNS&lt;/td&gt;
&lt;td&gt;Service discovery and DNS&lt;/td&gt;
&lt;td&gt;Cluster DNS for Kubernetes Services and pods&lt;/td&gt;
&lt;td&gt;Apache 2.0&lt;/td&gt;
&lt;td&gt;Graduated&lt;/td&gt;
&lt;td&gt;All Kubernetes clusters (default DNS server)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Submariner or Cilium Cluster Mesh&lt;/td&gt;
&lt;td&gt;Multi-cluster networking&lt;/td&gt;
&lt;td&gt;Cross-cluster pod connectivity and service discovery, with optional encryption&lt;/td&gt;
&lt;td&gt;Apache 2.0 (both)&lt;/td&gt;
&lt;td&gt;Submariner: Sandbox; Cilium: Graduated&lt;/td&gt;
&lt;td&gt;Clusters spanning multiple clouds or on-premises sites&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Control Plane&lt;/td&gt;
&lt;td&gt;Platform (orchestration, networking, and Day 2 operations combined)&lt;/td&gt;
&lt;td&gt;Running serverless, standard, stateful, cron, and VM workloads in one region or across regions and clouds, grouped in Control Plane’s Global Virtual Cloud (GVC)&lt;/td&gt;
&lt;td&gt;Proprietary (service)&lt;/td&gt;
&lt;td&gt;Not CNCF&lt;/td&gt;
&lt;td&gt;Teams that want production workloads with Day 2 operations handled and no clusters to operate. Limits: on Control Plane-managed regions the platform runs the CNI and its Istio-based mesh; clusters added through Bring Your Own Kubernetes (BYOK) keep their CNI but cannot run a separate mesh&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h2&gt;
  
  
  Which container management tools fit each scale?
&lt;/h2&gt;

&lt;p&gt;A home lab and a multi-cloud fleet need different management and networking tools.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Scale&lt;/th&gt;
&lt;th&gt;Management tool&lt;/th&gt;
&lt;th&gt;Networking tool&lt;/th&gt;
&lt;th&gt;Watch out for&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Single host or home lab&lt;/td&gt;
&lt;td&gt;Docker Compose or Podman with Portainer&lt;/td&gt;
&lt;td&gt;Docker bridge networking or Podman’s default Netavark network&lt;/td&gt;
&lt;td&gt;No high availability or automated failover&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;A few hosts with Compose stacks&lt;/td&gt;
&lt;td&gt;Docker Compose with a reverse proxy such as Traefik or Caddy&lt;/td&gt;
&lt;td&gt;Docker overlay network (requires Swarm mode), or host networking behind the reverse proxy&lt;/td&gt;
&lt;td&gt;Manual scaling; secrets management is often ad hoc&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;One production Kubernetes cluster&lt;/td&gt;
&lt;td&gt;Managed Kubernetes (EKS, GKE, AKS) or self-managed Kubernetes&lt;/td&gt;
&lt;td&gt;Cilium or Calico for CNI and network policy; CoreDNS for service discovery&lt;/td&gt;
&lt;td&gt;Cluster upgrades and node patching are ongoing work even with managed services&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Many clusters in one cloud&lt;/td&gt;
&lt;td&gt;Rancher (Fleet) or OpenShift with Red Hat Advanced Cluster Management, plus managed Kubernetes&lt;/td&gt;
&lt;td&gt;Cilium Cluster Mesh or VPC peering&lt;/td&gt;
&lt;td&gt;Policy consistency and RBAC sprawl across clusters; non-overlapping VPC and pod CIDRs must be planned up front&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Clusters across several clouds and on premises&lt;/td&gt;
&lt;td&gt;Rancher (Fleet) or OpenShift with Red Hat Advanced Cluster Management&lt;/td&gt;
&lt;td&gt;Submariner or Cilium Cluster Mesh for cross-cluster connectivity; Istio or Linkerd for mesh&lt;/td&gt;
&lt;td&gt;Pod CIDRs must not overlap for Cilium Cluster Mesh (Submariner needs Globalnet for overlapping ranges); cross-cloud latency and data transfer cost; certificate management at scale&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Teams that do not want to run clusters&lt;/td&gt;
&lt;td&gt;A managed platform that handles orchestration&lt;/td&gt;
&lt;td&gt;Managed by the platform&lt;/td&gt;
&lt;td&gt;Less control over runtime and networking internals&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;The &lt;a href="https://controlplane.com/blog/post/best-kubernetes-management-platforms?utm_source=devto&amp;amp;utm_medium=syndication&amp;amp;utm_campaign=best-container-management-networking-tools" rel="noopener noreferrer"&gt;best Kubernetes management platforms&lt;/a&gt; guide compares fleet managers in depth, and &lt;a href="https://controlplane.com/blog/post/best-kubernetes-alternatives?utm_source=devto&amp;amp;utm_medium=syndication&amp;amp;utm_campaign=best-container-management-networking-tools" rel="noopener noreferrer"&gt;the best Kubernetes alternatives&lt;/a&gt; covers teams deciding whether to run Kubernetes at all.&lt;/p&gt;

&lt;h2&gt;
  
  
  What are the layers of container networking?
&lt;/h2&gt;

&lt;p&gt;Container networking is a stack of layers, and each layer has its own tools and specifications. Knowing the layers helps you avoid gaps in security or observability and avoid adopting a service mesh when a network policy would do.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Layer&lt;/th&gt;
&lt;th&gt;What it does&lt;/th&gt;
&lt;th&gt;Common tools&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Container network interface (CNI) and pod networking&lt;/td&gt;
&lt;td&gt;Assigns IP addresses to pods and routes traffic between them across nodes&lt;/td&gt;
&lt;td&gt;Cilium, Calico, Flannel, Amazon VPC CNI, Azure CNI, GKE Dataplane V2 (Cilium-based)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Network policy&lt;/td&gt;
&lt;td&gt;Controls which pods can talk to which pods or external endpoints&lt;/td&gt;
&lt;td&gt;Kubernetes NetworkPolicy (enforced by the CNI), CiliumNetworkPolicy and CiliumClusterwideNetworkPolicy, Calico NetworkPolicy and GlobalNetworkPolicy&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Service discovery and DNS&lt;/td&gt;
&lt;td&gt;Resolves Service names to ClusterIPs, or to pod IPs for headless Services&lt;/td&gt;
&lt;td&gt;CoreDNS (Kubernetes default)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Ingress and Gateway API&lt;/td&gt;
&lt;td&gt;Routes external HTTP, gRPC, and TLS or TCP traffic to Services inside the cluster&lt;/td&gt;
&lt;td&gt;Envoy Gateway, Contour, Traefik, NGINX Gateway Fabric, Istio, Cilium&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Service mesh (mTLS, retries, traffic splitting)&lt;/td&gt;
&lt;td&gt;Encrypts and authenticates service-to-service traffic and adds retries, timeouts, and traffic management at the application layer&lt;/td&gt;
&lt;td&gt;Istio, Linkerd, Cilium Service Mesh&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Multi-cluster and cross-cloud connectivity&lt;/td&gt;
&lt;td&gt;Connects pods and Services across clusters in different networks, regions, or clouds&lt;/td&gt;
&lt;td&gt;Cilium Cluster Mesh, Submariner, cloud VPN or interconnect&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Egress control&lt;/td&gt;
&lt;td&gt;Restricts and audits outbound traffic from pods to external services&lt;/td&gt;
&lt;td&gt;Kubernetes NetworkPolicy egress rules, Cilium Egress Gateway, Calico egress gateways (Calico Enterprise and Calico Cloud), Istio egress gateway&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h3&gt;
  
  
  CNI choice: eBPF-based vs. iptables-based dataplanes
&lt;/h3&gt;

&lt;p&gt;The CNI plugin is the first networking decision for a Kubernetes cluster. Cilium uses eBPF programs in the Linux kernel for packet forwarding, network policy, and observability. With kube-proxy replacement enabled, Cilium handles Service load balancing in eBPF and avoids kube-proxy’s iptables rules, which grow with the number of Services. Calico’s eBPF dataplane can also replace kube-proxy, and kube-proxy’s nftables mode (GA in Kubernetes 1.33) reduces the same overhead. Flannel provides basic overlay networking and is the default CNI in K3s, but it does not enforce network policy on its own.&lt;/p&gt;

&lt;p&gt;For most production clusters, the choice comes down to Cilium or Calico. Cilium’s optional Hubble component provides flow-level observability. Calico has a long track record and a large installed base. Both are Apache 2.0 licensed. The right pick depends on kernel requirements, observability needs, and team familiarity, so test both with representative traffic before committing.&lt;/p&gt;

&lt;h3&gt;
  
  
  Service mesh choice: sidecar vs. ambient mode
&lt;/h3&gt;

&lt;p&gt;Istio and Linkerd both provide mTLS between services, retries, timeouts, and traffic telemetry. Linkerd uses lightweight Rust micro-proxies injected as sidecars. Istio’s ambient mode (GA since Istio 1.24) removes sidecars. A per-node ztunnel handles Layer 4 mTLS and authorization, and optional Envoy-based waypoint proxies handle Layer 7 policy. Istio still supports sidecar mode.&lt;/p&gt;

&lt;p&gt;A service mesh adds operational work. Adopt one when you need mutual TLS tied to service identity, application-layer traffic management, or per-request telemetry. If you only need encryption between nodes and basic network policy, the WireGuard encryption in Cilium and Calico is lighter. WireGuard encrypts traffic between nodes but provides no per-workload identity or request-level authorization, so use a mesh when policy must follow service identity. The guide on &lt;a href="https://controlplane.com/blog/post/container-orchestration-complexity-security?utm_source=devto&amp;amp;utm_medium=syndication&amp;amp;utm_campaign=best-container-management-networking-tools" rel="noopener noreferrer"&gt;container orchestration complexity and security&lt;/a&gt; covers this tradeoff in more depth.&lt;/p&gt;

&lt;h3&gt;
  
  
  Gateway API replacing Ingress
&lt;/h3&gt;

&lt;p&gt;Gateway API is the Kubernetes SIG Network successor to Ingress. The Ingress API is frozen but not deprecated. Gateway API splits routing into role-oriented resources, with a Gateway owned by platform operators and routes owned by application teams. The community ingress-nginx controller (kubernetes/ingress-nginx) was retired in March 2026; F5’s NGINX Ingress Controller is a separate project. New clusters should start with Gateway API. Traefik, Contour, Istio, and Kong serve both Ingress and Gateway API, so existing clusters can migrate route by route, and the ingress2gateway tool converts Ingress manifests to Gateway API resources.&lt;/p&gt;

&lt;h2&gt;
  
  
  How do you evaluate a container management or networking tool?
&lt;/h2&gt;

&lt;p&gt;Judge production readiness on governance, license, support, and operating cost, because feature lists say little about it.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Maturity and governance.&lt;/strong&gt; Graduation status and the number of maintaining companies show how durable a project is. Projects with a single corporate sponsor carry more risk of license changes or abandonment.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;License.&lt;/strong&gt; Apache 2.0 and MIT are permissive and well understood. The Business Source License, used by HashiCorp Nomad since 2023, restricts competing commercial use and may affect your legal review. Verify the license of every dependency, including transitive ones.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Support options.&lt;/strong&gt; Community support works for teams with deep expertise. Commercial support from the vendor or a third party matters for organizations with SLAs and compliance requirements.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Day 2 operations burden.&lt;/strong&gt; Upgrades, patching, certificate rotation, backup, and disaster recovery take more engineering time than setup. Check how each tool handles rolling upgrades and what breaks when an upgrade fails. The &lt;a href="https://controlplane.com/blog/post/kubernetes-production-architecture-upgrades-autoscaling-postgres?utm_source=devto&amp;amp;utm_medium=syndication&amp;amp;utm_campaign=best-container-management-networking-tools" rel="noopener noreferrer"&gt;Kubernetes production architecture&lt;/a&gt; guide covers this for Kubernetes.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Observability.&lt;/strong&gt; Check for Prometheus-format metrics and integration with your existing logging and tracing stack.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Security controls.&lt;/strong&gt; A default-deny network policy should be easy to apply per namespace or cluster-wide. Service-to-service mTLS should be easy to enforce; Linkerd enables it for meshed pods automatically, and Istio needs STRICT PeerAuthentication. Image scanning and admission control should be easy to enable.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Multi-cluster and multi-cloud support.&lt;/strong&gt; If you run more than one cluster or cloud, check for cross-cluster service discovery, policy federation, and encrypted connectivity between sites.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Test each candidate with representative workloads. Run upgrade and rollback cycles, simulate node failures and network partitions, and measure resource use under load.&lt;/p&gt;

&lt;h2&gt;
  
  
  How Control Plane fits
&lt;/h2&gt;

&lt;p&gt;Control Plane is the unbreakable platform for running production workloads. It runs serverless, standard, stateful, and cron workloads natively on AWS, GCP, Azure, and Oracle Cloud Infrastructure (OCI), VM workloads on locations joined through Control Plane’s Managed Kubernetes, and workloads on Kubernetes clusters you already run or your own machines, including on premises, active-active across regions and clouds.&lt;/p&gt;

&lt;p&gt;In the context of this guide, Control Plane replaces operating your own orchestrator, CNI, and service mesh in Control Plane-managed regions. Each workload runs in every location of its GVC. Each workload’s canonical endpoint uses DNS to route users to the nearest location where the workload passes its readiness probes, and Control Plane’s location routing options (routing tiers and latency offsets) shape where traffic goes.&lt;/p&gt;

&lt;p&gt;Security defaults are strict. A new workload has external inbound and outbound traffic disabled and the internal firewall closed until you allow it. Traffic between workloads uses mTLS with a unique client certificate per workload, rotated hourly. Control Plane provides an Istio-based service mesh out of the box. Control Plane is PCI DSS Level 1, SOC 2 Type II, HIPAA, and GDPR compliant.&lt;/p&gt;

&lt;p&gt;For private connectivity, Control Plane’s Cloud Wormhole runs agents inside your network that hold an outbound tunnel, so workloads can reach private databases and services in your VPCs or data centers without opening inbound ports. Native network resources also include AWS PrivateLink and Google Cloud Private Service Connect.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Limits.&lt;/strong&gt; On Control Plane-managed regions you do not choose the CNI or service mesh. If you need full control over the networking dataplane, self-managed Kubernetes with your choice of CNI and mesh is a better fit. Workloads that need their own kernel can run as VM workloads on locations joined through Control Plane’s Managed Kubernetes.&lt;/p&gt;

&lt;h2&gt;
  
  
  FAQ
&lt;/h2&gt;

&lt;p&gt;Short answers on container management, networking, and service mesh choices.&lt;/p&gt;

&lt;h3&gt;
  
  
  Where can I find the best in class container management and networking tools?
&lt;/h3&gt;

&lt;p&gt;Start at the &lt;a href="https://landscape.cncf.io/" rel="noopener noreferrer"&gt;CNCF Landscape&lt;/a&gt; and &lt;a href="https://artifacthub.io/" rel="noopener noreferrer"&gt;Artifact Hub&lt;/a&gt;. Filter by category, such as orchestration, CNI, or service mesh, and use graduated or incubating status as a maturity signal. Check project repositories for release cadence and community health, and use analyst reports for market context.&lt;/p&gt;

&lt;h3&gt;
  
  
  What is the best container management tool?
&lt;/h3&gt;

&lt;p&gt;Kubernetes, usually as a managed service such as EKS, GKE, or AKS, is the standard for production container management. Rancher and OpenShift add multi-cluster management and enterprise governance. For a few services on one host, Docker Compose or Podman with Portainer may be enough. The &lt;a href="https://controlplane.com/blog/post/best-kubernetes-management-platforms?utm_source=devto&amp;amp;utm_medium=syndication&amp;amp;utm_campaign=best-container-management-networking-tools" rel="noopener noreferrer"&gt;best Kubernetes management platforms&lt;/a&gt; guide compares the leading platforms in detail.&lt;/p&gt;

&lt;h3&gt;
  
  
  Is Cilium better than Calico?
&lt;/h3&gt;

&lt;p&gt;Neither wins for every cluster. Cilium suits teams that want eBPF-native networking and flow observability through Hubble, and Calico suits teams standardized on its policy model or an iptables or nftables dataplane. Calico also offers an eBPF dataplane. At high Service counts, any eBPF dataplane with kube-proxy replacement avoids kube-proxy’s iptables rule growth, and measured gains depend on kernel, workload, and configuration.&lt;/p&gt;

&lt;h3&gt;
  
  
  Do I need a service mesh?
&lt;/h3&gt;

&lt;p&gt;You need a service mesh if you require mutual TLS tied to service identity, per-request retries and timeouts, fine-grained traffic management, or application-layer telemetry. If node-to-node encryption and basic network policy are enough, WireGuard encryption in Cilium or Calico is lighter. A mesh adds proxy management, configuration work, and resource use.&lt;/p&gt;

&lt;h3&gt;
  
  
  What is the difference between Ingress and Gateway API?
&lt;/h3&gt;

&lt;p&gt;Gateway API is the role-oriented successor to Ingress. Ingress is a single resource for host and path HTTP routing and TLS termination, and anything more needs controller-specific annotations. Gateway API separates GatewayClass, Gateway, and route resources so platform operators and application teams own different pieces, and it defines route types for HTTP, gRPC, TLS, TCP, and UDP. Check each implementation’s conformance for the route types you need.&lt;/p&gt;

&lt;h3&gt;
  
  
  What is the best container management tool for a small team?
&lt;/h3&gt;

&lt;p&gt;A small team running a handful of services should start with Docker Compose or Podman and a management UI such as Portainer. If you need high availability or Kubernetes compatibility, a managed Kubernetes service runs the control plane for you. Teams that want to avoid cluster management can use a managed platform that handles orchestration.&lt;/p&gt;

&lt;h3&gt;
  
  
  How do containers in different clusters or clouds talk to each other?
&lt;/h3&gt;

&lt;p&gt;Multi-cluster networking tools connect pod networks and share service discovery between clusters. Cilium Cluster Mesh extends Cilium’s dataplane across clusters and requires non-overlapping pod CIDRs and node-to-node reachability. Submariner (CNCF Sandbox) builds IPsec or WireGuard tunnels between clusters and shares service discovery through a broker. Cloud VPN gateways and interconnects provide private links between regions and clouds.&lt;/p&gt;

&lt;h3&gt;
  
  
  How does Control Plane handle container networking?
&lt;/h3&gt;

&lt;p&gt;On Control Plane-managed regions you do not configure a CNI or service mesh; the platform runs these layers, and clusters added through BYOK keep their own CNI. Each workload’s canonical endpoint routes users to the nearest location where the workload passes its readiness probes. Workload-to-workload traffic is encrypted with mTLS using per-workload client certificates that rotate every hour, and new workloads start with external traffic disabled. Control Plane’s Cloud Wormhole reaches private databases and services in your networks through outbound tunnels.&lt;/p&gt;

&lt;h3&gt;
  
  
  Can I use Kubernetes and a managed platform together?
&lt;/h3&gt;

&lt;p&gt;Yes. Control Plane’s Managed Kubernetes and Bring Your Own Kubernetes (BYOK) let teams add their own clusters and machines as locations alongside Control Plane-managed regions. Some workloads run on infrastructure you control, and the platform handles Day 2 operations for the workloads in every location.&lt;/p&gt;

&lt;p&gt;Run production workloads in one region or across regions and clouds, with no clusters to operate. &lt;a href="https://controlplane.com/requestdemo?utm_source=devto&amp;amp;utm_medium=syndication&amp;amp;utm_campaign=best-container-management-networking-tools" rel="noopener noreferrer"&gt;Talk to the Control Plane team&lt;/a&gt; or &lt;a href="https://console.cpln.io/signup" rel="noopener noreferrer"&gt;sign up free&lt;/a&gt;.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Originally published on the &lt;a href="https://controlplane.com/blog/post/best-container-management-networking-tools?utm_source=devto&amp;amp;utm_medium=syndication&amp;amp;utm_campaign=best-container-management-networking-tools" rel="noopener noreferrer"&gt;Control Plane blog&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>kubernetes</category>
      <category>containers</category>
      <category>networking</category>
      <category>devops</category>
    </item>
    <item>
      <title>Which Cluster Manager Is Best for Scaling Workloads? Kubernetes, Nomad, Slurm, Ray, and More by Workload Type (2026)</title>
      <dc:creator>Noah Grinstein</dc:creator>
      <pubDate>Tue, 17 Nov 2026 22:56:45 +0000</pubDate>
      <link>https://dev.to/noahcontrolplane/which-cluster-manager-is-best-for-scaling-workloads-kubernetes-nomad-slurm-ray-and-more-by-2n26</link>
      <guid>https://dev.to/noahcontrolplane/which-cluster-manager-is-best-for-scaling-workloads-kubernetes-nomad-slurm-ray-and-more-by-2n26</guid>
      <description>&lt;p&gt;For long-running services and APIs, Kubernetes through a managed service such as EKS, GKE, or AKS is the best cluster manager for scaling because it autoscales pods and nodes on CPU, memory, and custom metrics such as request rate. For batch HPC and large AI training, use Slurm. For distributed Python and AI pipelines, use Ray. For mixed containers and plain binaries with less operational work, use Nomad. The right choice depends on what you are scaling, what triggers that scaling, and how machines get added underneath. This guide compares the major cluster managers on those points, matches them to workload types, and lists the practical limits that stop scaling before the scheduler does.&lt;/p&gt;

&lt;p&gt;Disclosure: Control Plane publishes this guide.&lt;/p&gt;

&lt;h2&gt;
  
  
  TL;DR
&lt;/h2&gt;

&lt;p&gt;Kubernetes is the best cluster manager for scaling cloud-native services and APIs. For batch, HPC, and Python AI work, the best choice changes with the workload.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Kubernetes&lt;/strong&gt; (managed EKS, GKE, or AKS; OpenShift or Rancher for self-managed fleets) is the default for web services, APIs, and event-driven workers.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Slurm&lt;/strong&gt; is the standard for HPC, tightly coupled simulations, and large-scale GPU training on fixed or cloud-bursting clusters.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Ray&lt;/strong&gt; is purpose-built for distributed Python AI pipelines, hyperparameter tuning, and batch inference, and it runs on Kubernetes, Slurm, or cloud VMs.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Nomad&lt;/strong&gt; handles mixed containers, binaries, and legacy apps with a simpler operational model.&lt;/li&gt;
&lt;li&gt;Scaling has two layers, workload scaling (pods, tasks, jobs, actors) and machine scaling (nodes, instances), and each layer needs its own cap.&lt;/li&gt;
&lt;li&gt;Cloud quotas, API server load, IP exhaustion, and downstream systems usually stop scaling before the scheduler’s documented ceiling.&lt;/li&gt;
&lt;li&gt;Control Plane runs services, APIs, workers, stateful workloads, and cron jobs with workload autoscaling built in, on one cloud, many clouds, or your own infrastructure, and teams never have to operate a Kubernetes cluster.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Which cluster manager is best for scaling workloads?
&lt;/h2&gt;

&lt;p&gt;Each cluster manager scales a different unit on different signals. A Kubernetes Horizontal Pod Autoscaler (HPA) watches CPU, memory, or custom metrics and adds pod replicas, while a Cluster Autoscaler or Karpenter provisions nodes to fit those pods. Slurm queues jobs and powers on or cloud-bursts nodes through its ResumeProgram to fit them, and it does not grow a job once it starts. Ray scales tasks and actors through its own autoscaler or KubeRay, and Nomad scales task groups through the Nomad Autoscaler with APM plugins. Docker Swarm lets you set replica counts manually but has no built-in autoscaler.&lt;/p&gt;

&lt;p&gt;The systems were designed for different scaling patterns. Kubernetes assumes elastic infrastructure. Slurm assumes a fixed or semi-fixed cluster with queued batch work. Ray assumes a Python-native programming model where the framework manages distribution. Nomad assumes you want broad workload support with minimal operational overhead.&lt;/p&gt;

&lt;p&gt;Scale figures come from each project’s or provider’s official documentation, checked in November 2026.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Cluster manager&lt;/th&gt;
&lt;th&gt;Unit that scales&lt;/th&gt;
&lt;th&gt;What triggers scaling&lt;/th&gt;
&lt;th&gt;How it adds machines&lt;/th&gt;
&lt;th&gt;Documented scale limits&lt;/th&gt;
&lt;th&gt;Best fit&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Kubernetes (upstream)&lt;/td&gt;
&lt;td&gt;Pod replicas (HPA, KEDA); pod CPU and memory requests (VPA)&lt;/td&gt;
&lt;td&gt;CPU, memory, custom metrics, external metrics, event sources&lt;/td&gt;
&lt;td&gt;Cluster Autoscaler or Karpenter provisions nodes from cloud provider&lt;/td&gt;
&lt;td&gt;Designed for up to 5,000 nodes, 150,000 pods, and 110 pods per node&lt;/td&gt;
&lt;td&gt;Long-running services, APIs, event-driven workers&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;GKE (managed Kubernetes)&lt;/td&gt;
&lt;td&gt;Pods&lt;/td&gt;
&lt;td&gt;Same as upstream plus GKE-specific metrics&lt;/td&gt;
&lt;td&gt;GKE node auto-provisioning&lt;/td&gt;
&lt;td&gt;Up to 65,000 nodes on GKE Standard, with extra requirements above 5,000 and 15,000 nodes; 5,000 on Autopilot&lt;/td&gt;
&lt;td&gt;Services on Google Cloud&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;EKS (managed Kubernetes)&lt;/td&gt;
&lt;td&gt;Pods&lt;/td&gt;
&lt;td&gt;Same as upstream&lt;/td&gt;
&lt;td&gt;Karpenter or Cluster Autoscaler with managed node groups&lt;/td&gt;
&lt;td&gt;Up to 100,000 nodes per cluster with AWS account team support; adjustable default quotas of 30 managed node groups and 450 nodes per group&lt;/td&gt;
&lt;td&gt;Services on AWS&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;AKS (managed Kubernetes)&lt;/td&gt;
&lt;td&gt;Pods&lt;/td&gt;
&lt;td&gt;Same as upstream&lt;/td&gt;
&lt;td&gt;AKS cluster autoscaler&lt;/td&gt;
&lt;td&gt;Up to 5,000 nodes per cluster and 1,000 per node pool&lt;/td&gt;
&lt;td&gt;Services on Azure&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;HashiCorp Nomad&lt;/td&gt;
&lt;td&gt;Task groups&lt;/td&gt;
&lt;td&gt;Nomad Autoscaler with APM plugins (Prometheus, Datadog, others)&lt;/td&gt;
&lt;td&gt;Cluster scaling target provisions cloud instances&lt;/td&gt;
&lt;td&gt;Production clusters of more than 10,000 nodes; 2 million containers on 6,100 hosts in a 2020 benchmark&lt;/td&gt;
&lt;td&gt;Mixed containers, binaries, batch&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Docker Swarm&lt;/td&gt;
&lt;td&gt;Service replicas&lt;/td&gt;
&lt;td&gt;Manual (&lt;code&gt;docker service scale&lt;/code&gt;); no built-in autoscaler&lt;/td&gt;
&lt;td&gt;Manual node addition; no built-in machine scaling&lt;/td&gt;
&lt;td&gt;No published scale limit&lt;/td&gt;
&lt;td&gt;Small teams, simple deployments&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Slurm&lt;/td&gt;
&lt;td&gt;Jobs and job steps&lt;/td&gt;
&lt;td&gt;Pending jobs allocated to powered-down or cloud nodes&lt;/td&gt;
&lt;td&gt;ResumeProgram starts nodes on demand; SuspendProgram powers them down&lt;/td&gt;
&lt;td&gt;Large-system guidance cites 1,966,080 tasks on 122,880 compute nodes; runs exascale systems such as Frontier&lt;/td&gt;
&lt;td&gt;HPC, tightly coupled simulations, large AI training&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;IBM Spectrum LSF&lt;/td&gt;
&lt;td&gt;Jobs&lt;/td&gt;
&lt;td&gt;Job queue policies and resource demand&lt;/td&gt;
&lt;td&gt;Resource Connector borrows cloud instances&lt;/td&gt;
&lt;td&gt;No published scale limit&lt;/td&gt;
&lt;td&gt;Enterprise HPC and AI training&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Ray&lt;/td&gt;
&lt;td&gt;Tasks and actors&lt;/td&gt;
&lt;td&gt;Ray autoscaler acts on pending logical resource requests from tasks and actors&lt;/td&gt;
&lt;td&gt;Ray Autoscaler requests nodes from cloud provider or KubeRay requests pods&lt;/td&gt;
&lt;td&gt;Tested envelope of 2,000+ nodes, 40,000+ actors, and 10,000+ concurrent tasks&lt;/td&gt;
&lt;td&gt;Distributed Python AI pipelines, hyperparameter tuning&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Apache Spark on Kubernetes or YARN&lt;/td&gt;
&lt;td&gt;Executors&lt;/td&gt;
&lt;td&gt;Dynamic allocation on pending tasks and idle executors; on Kubernetes it needs shuffle tracking or decommissioning&lt;/td&gt;
&lt;td&gt;On Kubernetes, the cluster autoscaler adds nodes; on YARN, NodeManagers must already exist&lt;/td&gt;
&lt;td&gt;No fixed executor cap; bounded by the underlying cluster&lt;/td&gt;
&lt;td&gt;Large-scale data processing, SQL analytics&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Fleet tools such as Rancher and OpenShift add multi-cluster management on top of Kubernetes; our &lt;a href="https://controlplane.com/blog/post/best-kubernetes-management-platforms?utm_source=devto&amp;amp;utm_medium=syndication&amp;amp;utm_campaign=best-cluster-manager-scaling-workloads" rel="noopener noreferrer"&gt;Kubernetes management platforms roundup&lt;/a&gt; compares them.&lt;/p&gt;

&lt;h2&gt;
  
  
  Which cluster manager fits each workload type?
&lt;/h2&gt;

&lt;p&gt;A web API absorbing traffic spikes and a training job that needs 256 GPUs at once need different schedulers.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Workload&lt;/th&gt;
&lt;th&gt;Best fit&lt;/th&gt;
&lt;th&gt;Why&lt;/th&gt;
&lt;th&gt;Watch out for&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Web services and APIs&lt;/td&gt;
&lt;td&gt;Kubernetes (managed)&lt;/td&gt;
&lt;td&gt;HPA scales pods on CPU and memory, and on request rate or latency through a metrics adapter or KEDA; rolling updates keep services live during deploys&lt;/td&gt;
&lt;td&gt;Requires cluster operations expertise or a managed service; networking complexity grows with cluster size&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Event-driven and queue workers&lt;/td&gt;
&lt;td&gt;Kubernetes with KEDA&lt;/td&gt;
&lt;td&gt;KEDA scales pods from zero based on queue depth, stream lag, or custom triggers&lt;/td&gt;
&lt;td&gt;Scaling from zero adds cold-start latency; monitoring queue-based triggers requires careful tuning&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Batch and cron jobs&lt;/td&gt;
&lt;td&gt;Kubernetes (Job and CronJob) or Slurm&lt;/td&gt;
&lt;td&gt;Kubernetes handles cloud-native batch; Slurm handles large-scale batch with priority queues and preemption&lt;/td&gt;
&lt;td&gt;Native gang scheduling is beta and off by default in recent Kubernetes releases; most teams use Kueue or Volcano for all-or-nothing scheduling&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;HPC and tightly coupled simulations&lt;/td&gt;
&lt;td&gt;Slurm&lt;/td&gt;
&lt;td&gt;All-or-nothing multi-node allocation, topology-aware placement, fine-grained GPU control, mature queue policies such as fair share and backfill&lt;/td&gt;
&lt;td&gt;Slurm assumes HPC domain knowledge; cloud bursting adds complexity&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Large AI model training on GPUs&lt;/td&gt;
&lt;td&gt;Slurm&lt;/td&gt;
&lt;td&gt;Exclusive node and GPU allocation through GRES and cgroups; topology-aware placement on the interconnect; native MPI launch through srun and PMIx&lt;/td&gt;
&lt;td&gt;Requires dedicated or reserved GPU infrastructure for cost efficiency&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Distributed Python data and AI pipelines&lt;/td&gt;
&lt;td&gt;Ray (on Kubernetes, Slurm, or VMs)&lt;/td&gt;
&lt;td&gt;Native Python API for tasks, actors, and libraries like Ray Train and Ray Tune; autoscales workers&lt;/td&gt;
&lt;td&gt;Ray needs a host, such as KubeRay on Kubernetes, Slurm, or cloud VMs through the Ray cluster launcher; on KubeRay, configure the Kubernetes cluster autoscaler too&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Mixed containers, binaries, and legacy apps&lt;/td&gt;
&lt;td&gt;Nomad&lt;/td&gt;
&lt;td&gt;Single scheduler handles Docker containers, raw binaries, Java apps, and system jobs&lt;/td&gt;
&lt;td&gt;Smaller ecosystem than Kubernetes; fewer third-party integrations and operators&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Small teams without Kubernetes skills&lt;/td&gt;
&lt;td&gt;Docker Swarm or Nomad&lt;/td&gt;
&lt;td&gt;Swarm is built into Docker; Nomad has a gentler learning curve than Kubernetes&lt;/td&gt;
&lt;td&gt;Swarm has no autoscaling and no published scale limit; Nomad’s ecosystem is smaller&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Teams deciding whether they need Kubernetes at all can compare the trade-offs in our guide to &lt;a href="https://controlplane.com/blog/post/best-kubernetes-alternatives?utm_source=devto&amp;amp;utm_medium=syndication&amp;amp;utm_campaign=best-cluster-manager-scaling-workloads" rel="noopener noreferrer"&gt;Kubernetes alternatives&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  How do workload scaling and machine scaling work together?
&lt;/h2&gt;

&lt;p&gt;Workload scaling decides how many units of work run, and machine scaling decides how many machines run them.&lt;/p&gt;

&lt;p&gt;The first layer is workload scaling. In Kubernetes, the Horizontal Pod Autoscaler adds pod replicas when CPU, memory, or a custom metric crosses a threshold. In Slurm, a new job enters the queue and waits for resources. In Ray, the application submits tasks and actors, and Ray Serve scales model replicas.&lt;/p&gt;

&lt;p&gt;The second layer is machine scaling. When the workload layer requests more capacity than the cluster has, something needs to add machines. Kubernetes relies on Cluster Autoscaler or Karpenter to provision new nodes from the cloud provider. Slurm uses ResumeProgram to power on or provision nodes. Nomad’s cluster scaling target calls out to cloud APIs. Ray’s autoscaler can request new nodes directly or, through KubeRay, let Kubernetes handle it.&lt;/p&gt;

&lt;p&gt;Both layers need caps. An HPA with maxReplicas set far above real demand, paired with a Cluster Autoscaler or Karpenter NodePool with no node or CPU limit, keeps adding nodes until a cloud quota stops it. A Slurm cluster without SuspendTime and SuspendProgram leaves idle GPU nodes running. Cap maxReplicas on the workload layer, and set a maximum node count, node group size, or NodePool limit on the machine layer.&lt;/p&gt;

&lt;p&gt;The &lt;a href="https://controlplane.com/blog/post/kubernetes-autoscaling-tools?utm_source=devto&amp;amp;utm_medium=syndication&amp;amp;utm_campaign=best-cluster-manager-scaling-workloads" rel="noopener noreferrer"&gt;Kubernetes autoscaling tools guide&lt;/a&gt; covers HPA, VPA, KEDA, Cluster Autoscaler, and Karpenter in detail.&lt;/p&gt;

&lt;h2&gt;
  
  
  What limits scaling in practice?
&lt;/h2&gt;

&lt;p&gt;The documented node and pod limits of your cluster manager are rarely the bottleneck. Practical scaling limits come from the infrastructure and systems around the scheduler.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Limit&lt;/th&gt;
&lt;th&gt;Where it shows up&lt;/th&gt;
&lt;th&gt;How to raise it&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Cloud quotas and instance availability&lt;/td&gt;
&lt;td&gt;Cloud provider rejects instance launch requests; GPU instances unavailable in your region&lt;/td&gt;
&lt;td&gt;Request quota increases in advance; use multiple regions or availability zones; reserve capacity&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Kubernetes API server load&lt;/td&gt;
&lt;td&gt;API server becomes slow or returns 429 errors under high object churn&lt;/td&gt;
&lt;td&gt;Use a managed Kubernetes control plane (EKS, GKE, AKS) that scales the API server with load; reduce object churn and broad watches; split very large fleets across clusters&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;IP address exhaustion in the pod network&lt;/td&gt;
&lt;td&gt;New pods stick in ContainerCreating with IP assignment errors because the subnet has no free addresses&lt;/td&gt;
&lt;td&gt;Add larger subnets or secondary CIDR ranges (EKS custom networking, GKE additional Pod ranges); use an overlay CNI mode (Azure CNI Overlay, Cilium); move pods to IPv6&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Scheduler throughput&lt;/td&gt;
&lt;td&gt;Pods or jobs wait in queue because the scheduler cannot evaluate placements fast enough&lt;/td&gt;
&lt;td&gt;Lower percentageOfNodesToScore on self-managed Kubernetes control planes; limit costly inter-pod affinity rules; in Slurm, tune backfill settings; split very large fleets across clusters&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Image pull time&lt;/td&gt;
&lt;td&gt;Pods on new nodes take minutes to start because images are large&lt;/td&gt;
&lt;td&gt;Use smaller base images, registry pull-through caches, pre-pulled images, or lazy loading (GKE image streaming, SOCI on AWS)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Database and downstream connection limits&lt;/td&gt;
&lt;td&gt;Application scales but the database rejects new connections or the downstream API throttles&lt;/td&gt;
&lt;td&gt;Keep maximum replicas times pool size below the database’s connection limit; use a pooler such as PgBouncer or RDS Proxy; add read replicas; add backpressure and circuit breakers&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Cost guardrails (max node counts)&lt;/td&gt;
&lt;td&gt;Platform team sets a maximum node count to control spend; autoscaler stops adding nodes&lt;/td&gt;
&lt;td&gt;Review guardrails against actual demand; use per-namespace resource quotas for finer control&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h2&gt;
  
  
  How Control Plane fits
&lt;/h2&gt;

&lt;p&gt;Control Plane is the unbreakable platform for running production workloads. It runs serverless, standard, stateful, and cron workloads natively on AWS, GCP, Azure, and Oracle Cloud Infrastructure (OCI), VM workloads on locations joined through Control Plane’s Managed Kubernetes, and workloads on Kubernetes clusters you already run or your own machines, including on premises, active-active across regions and clouds.&lt;/p&gt;

&lt;p&gt;In Control Plane-managed regions, the platform scales the machines underneath and you set scaling rules per workload. Control Plane runs services, APIs, workers, stateful workloads, and cron jobs. Slurm and Ray stay the schedulers for tightly coupled HPC and large distributed training, and Control Plane runs the services around them.&lt;/p&gt;

&lt;p&gt;Workload autoscaling strategies include requests per second, CPU, memory, latency, concurrency, multi-metric, and KEDA. Concurrency applies to serverless workloads only, and serverless workloads do not use latency or multi-metric scaling. Serverless workloads scale to zero on requests per second or concurrency. Standard and stateful workloads scale to zero through KEDA, enabled per Global Virtual Cloud (GVC), Control Plane’s named set of locations. Cron workloads never scale to zero, and VM workloads use fixed minScale and maxScale.&lt;/p&gt;

&lt;p&gt;minScale and maxScale apply per location, so a workload deployed to three locations can run up to three times its maxScale.&lt;/p&gt;

&lt;p&gt;Capacity AI, Control Plane’s automatic CPU and memory sizing, right-sizes reservations from historical usage; it does not work with CPU-based or multi-metric autoscaling, or with GPUs.&lt;/p&gt;

&lt;p&gt;Control Plane is PCI DSS Level 1, SOC 2 Type II, HIPAA, and GDPR compliant. Control Plane handles Day 2 operations for you, including autoscaling, built-in observability, and security.&lt;/p&gt;

&lt;p&gt;Teams that want the &lt;a href="https://controlplane.com/blog/post/kubernetes-benefits-without-platform-team?utm_source=devto&amp;amp;utm_medium=syndication&amp;amp;utm_campaign=best-cluster-manager-scaling-workloads" rel="noopener noreferrer"&gt;benefits of Kubernetes without a platform team&lt;/a&gt; have no node groups or cluster autoscalers to tune.&lt;/p&gt;

&lt;h2&gt;
  
  
  FAQ
&lt;/h2&gt;

&lt;p&gt;Short answers on cluster managers, node limits, and Control Plane scaling.&lt;/p&gt;

&lt;h3&gt;
  
  
  Which cluster manager is best for scaling workloads?
&lt;/h3&gt;

&lt;p&gt;Kubernetes, delivered as a managed service like EKS, GKE, or AKS, is the best cluster manager for scaling long-running services and APIs because it autoscales both pods and nodes on many signals. For HPC and large AI training, Slurm is the best choice. For distributed Python AI pipelines, Ray is the best runtime, and it runs on Kubernetes, Slurm, or cloud VMs. For mixed containers and binaries, Nomad offers scaling with less operational overhead.&lt;/p&gt;

&lt;h3&gt;
  
  
  Is Kubernetes better than Nomad for scaling?
&lt;/h3&gt;

&lt;p&gt;Kubernetes is better for autoscaling depth, with more scaling triggers and a larger set of scaling tools (HPA, VPA, KEDA, Karpenter). Nomad documents production clusters of more than 10,000 nodes, above the upstream Kubernetes design target of 5,000, and it schedules binaries and VMs alongside containers with less operational work. Pick Kubernetes for the ecosystem and Nomad for a smaller operational footprint.&lt;/p&gt;

&lt;h3&gt;
  
  
  What is the difference between Slurm and Kubernetes?
&lt;/h3&gt;

&lt;p&gt;Slurm is a batch job scheduler designed for HPC clusters with fixed or semi-fixed resources, queue-based scheduling, gang scheduling, and topology-aware GPU placement. Kubernetes is a container orchestration platform designed for elastic cloud infrastructure with autoscaling, service discovery, and rolling deployments. Slurm excels at large-scale training and simulation. Kubernetes excels at services, APIs, and cloud-native pipelines. Many organizations run both.&lt;/p&gt;

&lt;h3&gt;
  
  
  Can Kubernetes run HPC or AI training jobs?
&lt;/h3&gt;

&lt;p&gt;Yes, Kubernetes can run HPC and AI training jobs. Kueue and Volcano add all-or-nothing scheduling and fair-share queuing, and GPU partitioning comes through MIG and Dynamic Resource Allocation. Slurm’s topology-aware placement and queue policies such as backfill are built in and more mature. For smaller runs or teams already on Kubernetes, Kubernetes works well; for tightly coupled training on hundreds of GPUs, Slurm is the more mature choice.&lt;/p&gt;

&lt;h3&gt;
  
  
  What is Ray used for?
&lt;/h3&gt;

&lt;p&gt;Ray is a distributed computing runtime for Python-native AI workloads. It provides libraries for distributed training (Ray Train), hyperparameter tuning (Ray Tune), batch inference, reinforcement learning, and data processing. It runs on Kubernetes (through KubeRay), Slurm, or cloud VMs, and its autoscaler adds and removes worker nodes or pods on whatever infrastructure hosts it.&lt;/p&gt;

&lt;h3&gt;
  
  
  How many nodes can a Kubernetes cluster have?
&lt;/h3&gt;

&lt;p&gt;Upstream Kubernetes is designed for up to 5,000 nodes and 150,000 pods per cluster. GKE Standard supports up to 65,000 nodes and EKS up to 100,000 on their own control planes. AKS supports up to 5,000. In practice, most organizations hit cloud quotas, API server load, or IP address exhaustion before reaching these node limits.&lt;/p&gt;

&lt;h3&gt;
  
  
  Do I need a cluster manager at all?
&lt;/h3&gt;

&lt;p&gt;If you are running a handful of containers on a single machine, Docker Compose or a systemd-based deployment may be enough. A cluster manager becomes necessary when you need to distribute workloads across multiple machines, autoscale based on demand, handle failures automatically, or manage resource contention across teams. For services and APIs, Control Plane gives you workload autoscaling on any cloud or your own infrastructure without operating a cluster.&lt;/p&gt;

&lt;h3&gt;
  
  
  How does Control Plane scale workloads?
&lt;/h3&gt;

&lt;p&gt;Control Plane scales each workload’s replicas on requests per second, CPU, memory, latency, concurrency (serverless only), multi-metric rules, or KEDA, and the platform provisions the machines underneath. You set minScale and maxScale once per workload, and they apply in every location of its GVC. Serverless workloads scale to zero on request or concurrency signals, standard and stateful workloads scale to zero through KEDA, and Capacity AI right-sizes CPU and memory reservations for workloads that do not autoscale on CPU or multiple metrics or use GPUs.&lt;/p&gt;

&lt;h3&gt;
  
  
  Can Slurm and Kubernetes coexist?
&lt;/h3&gt;

&lt;p&gt;Yes. A common pattern runs Slurm for large GPU training jobs that need all-or-nothing allocation and topology-aware placement, and Kubernetes for model serving, APIs, MLOps pipelines, and monitoring. Projects such as SchedMD’s Slinky run Slurm on Kubernetes, and Ray runs on either.&lt;/p&gt;

&lt;p&gt;Run services, APIs, and workers on any cloud without managing clusters. &lt;a href="https://controlplane.com/requestdemo?utm_source=devto&amp;amp;utm_medium=syndication&amp;amp;utm_campaign=best-cluster-manager-scaling-workloads" rel="noopener noreferrer"&gt;Talk to the Control Plane team&lt;/a&gt; or &lt;a href="https://console.cpln.io/signup" rel="noopener noreferrer"&gt;sign up free&lt;/a&gt;.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Originally published on the &lt;a href="https://controlplane.com/blog/post/best-cluster-manager-scaling-workloads?utm_source=devto&amp;amp;utm_medium=syndication&amp;amp;utm_campaign=best-cluster-manager-scaling-workloads" rel="noopener noreferrer"&gt;Control Plane blog&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>kubernetes</category>
      <category>devops</category>
      <category>cloud</category>
      <category>scaling</category>
    </item>
    <item>
      <title>Platforms That Run Containers and Full VMs Across Multiple Clouds (2026): OpenShift Virtualization, Harvester, and More</title>
      <dc:creator>Noah Grinstein</dc:creator>
      <pubDate>Tue, 17 Nov 2026 22:56:11 +0000</pubDate>
      <link>https://dev.to/noahcontrolplane/platforms-that-run-containers-and-full-vms-across-multiple-clouds-2026-openshift-virtualization-3pjn</link>
      <guid>https://dev.to/noahcontrolplane/platforms-that-run-containers-and-full-vms-across-multiple-clouds-2026-openshift-virtualization-3pjn</guid>
      <description>&lt;p&gt;Platforms that run containers and full VMs side by side across clouds either run VMs inside Kubernetes using KubeVirt, run a traditional hypervisor with Kubernetes layered on top, or manage separate VM and container systems from one console. Pick by where your VMs run today and whether you want one unified runtime or one unified console. This guide compares each platform on how VMs run, which clouds each one reaches, what cloud hardware VMs require, and how VM images move in.&lt;/p&gt;

&lt;p&gt;Disclosure: Control Plane publishes this guide.&lt;/p&gt;

&lt;h2&gt;
  
  
  TL;DR
&lt;/h2&gt;

&lt;p&gt;The choice comes down to where your VMs run today and which execution model your team can operate.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Three models exist: VMs inside Kubernetes (KubeVirt), hypervisor-first with Kubernetes on top, and a management console over separate VM and container systems.&lt;/li&gt;
&lt;li&gt;KubeVirt is the common engine behind most Kubernetes-native VM platforms, turning a VM into a Kubernetes pod backed by KVM.&lt;/li&gt;
&lt;li&gt;KubeVirt VMs in public clouds need bare-metal instances or instances that support nested virtualization, which narrows instance choice and region availability.&lt;/li&gt;
&lt;li&gt;Broadcom’s VMware licensing changes are a major reason enterprises are evaluating these platforms.&lt;/li&gt;
&lt;li&gt;Choose by matching your current hypervisor dependencies, target clouds, team skills, and migration complexity.&lt;/li&gt;
&lt;li&gt;Control Plane fits as a KubeVirt-based option that runs VM workloads on locations joined through Control Plane’s Managed Kubernetes and runs containers in its managed regions on AWS, GCP, Azure, and Oracle Cloud Infrastructure (OCI), under one API and policy set.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Which platform runs both containers and full VMs across multiple clouds?
&lt;/h2&gt;

&lt;p&gt;Several platforms answer this question with different architectures. Some run VMs inside a Kubernetes cluster as pods, others start with a hypervisor and add Kubernetes on top, and a third group keeps VM and container systems separate under one management console. Nine platforms compare as follows on the criteria that decide the choice.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Platform&lt;/th&gt;
&lt;th&gt;How VMs run&lt;/th&gt;
&lt;th&gt;Where it runs&lt;/th&gt;
&lt;th&gt;Cloud hardware needed for VMs&lt;/th&gt;
&lt;th&gt;VM image import&lt;/th&gt;
&lt;th&gt;Best fit&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Red Hat OpenShift Virtualization&lt;/td&gt;
&lt;td&gt;KubeVirt on Kubernetes&lt;/td&gt;
&lt;td&gt;On premises, AWS (incl. ROSA, bare metal), Azure (ARO), Google Cloud (bare-metal nodes), IBM Cloud (bare metal), OCI&lt;/td&gt;
&lt;td&gt;Bare-metal instances; on Azure (ARO), specific supported VM sizes&lt;/td&gt;
&lt;td&gt;Migration Toolkit for Virtualization (from vSphere, Hyper-V, OpenStack, Red Hat Virtualization, OVA, AWS EC2); disk images via CDI&lt;/td&gt;
&lt;td&gt;Enterprises standardizing on OpenShift and the Red Hat ecosystem&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;SUSE Virtualization (Harvester) with SUSE Rancher Prime&lt;/td&gt;
&lt;td&gt;KubeVirt on Kubernetes (HCI appliance)&lt;/td&gt;
&lt;td&gt;On premises, edge&lt;/td&gt;
&lt;td&gt;Bare-metal servers&lt;/td&gt;
&lt;td&gt;qcow2, raw, ISO; VMware, OpenStack, and OVA imports through the VM Import Controller add-on&lt;/td&gt;
&lt;td&gt;On-premises and edge deployments seeking open-source HCI&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;VMware Cloud Foundation with vSphere Kubernetes Service&lt;/td&gt;
&lt;td&gt;ESXi hypervisor with Kubernetes clusters running as VMs&lt;/td&gt;
&lt;td&gt;On premises; VMware workloads also run on VMware Cloud on AWS, Azure VMware Solution, and Google Cloud VMware Engine (Kubernetes support varies by service)&lt;/td&gt;
&lt;td&gt;Certified servers on premises; provider-managed hosts on VMware Cloud on AWS, Azure VMware Solution, and Google Cloud VMware Engine&lt;/td&gt;
&lt;td&gt;Native vSphere formats (VMDK, OVF)&lt;/td&gt;
&lt;td&gt;Organizations preserving existing VMware operations&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Nutanix Cloud Platform with Nutanix Kubernetes Platform&lt;/td&gt;
&lt;td&gt;AHV hypervisor with Kubernetes clusters running as VMs&lt;/td&gt;
&lt;td&gt;On premises, Nutanix Cloud Clusters on AWS, Azure, Google Cloud, and OVHcloud&lt;/td&gt;
&lt;td&gt;Nutanix-certified bare-metal nodes&lt;/td&gt;
&lt;td&gt;Nutanix Move (from vSphere, Hyper-V, AWS, and others)&lt;/td&gt;
&lt;td&gt;Enterprises refreshing hardware and consolidating HCI&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Google Distributed Cloud&lt;/td&gt;
&lt;td&gt;KubeVirt (VM Runtime on Google Distributed Cloud)&lt;/td&gt;
&lt;td&gt;On premises and edge (software-only for bare metal), managed from Google Cloud&lt;/td&gt;
&lt;td&gt;Bare-metal servers&lt;/td&gt;
&lt;td&gt;qcow2, VMDK via image import&lt;/td&gt;
&lt;td&gt;Google Cloud-aligned organizations running VMs on premises&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Spectro Cloud Palette Virtual Machine Orchestrator&lt;/td&gt;
&lt;td&gt;KubeVirt on Kubernetes&lt;/td&gt;
&lt;td&gt;On premises (bare metal, MAAS), edge, air-gapped&lt;/td&gt;
&lt;td&gt;Bare-metal servers&lt;/td&gt;
&lt;td&gt;qcow2, VMDK, VHDX via KubeVirt CDI&lt;/td&gt;
&lt;td&gt;Multi-cluster Kubernetes teams needing VM support on their own hardware&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Mirantis k0rdent Virtualization&lt;/td&gt;
&lt;td&gt;KubeVirt on Kubernetes&lt;/td&gt;
&lt;td&gt;On premises; any k0rdent-managed cluster with KVM-capable nodes&lt;/td&gt;
&lt;td&gt;Bare-metal or nested-virt instances&lt;/td&gt;
&lt;td&gt;qcow2, VMDK, VHDX via KubeVirt CDI&lt;/td&gt;
&lt;td&gt;Teams seeking open-source Kubernetes with VM support&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;HPE Morpheus&lt;/td&gt;
&lt;td&gt;Management layer over separate hypervisors and Kubernetes clusters&lt;/td&gt;
&lt;td&gt;On premises, AWS, Azure, Google Cloud, OCI&lt;/td&gt;
&lt;td&gt;Depends on underlying hypervisor&lt;/td&gt;
&lt;td&gt;Managed through connected hypervisor or cloud provider&lt;/td&gt;
&lt;td&gt;Organizations wanting one console without re-platforming VMs&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Control Plane&lt;/td&gt;
&lt;td&gt;KubeVirt on Control Plane Managed Kubernetes locations&lt;/td&gt;
&lt;td&gt;Containers: AWS, GCP, Azure, OCI. VMs: Control Plane Managed Kubernetes locations with KVM-capable nodes, such as on AWS or your own servers&lt;/td&gt;
&lt;td&gt;KVM-capable nodes: AWS .metal or c8i/m8i/r8i nested-virt instances, or own KVM hosts&lt;/td&gt;
&lt;td&gt;qcow2, raw, VMDK, VHD/VHDX, VDI, ISO; HTTP(S) import with conversion, or container disk image&lt;/td&gt;
&lt;td&gt;Teams running containers across clouds that also need VM workloads under one API&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h2&gt;
  
  
  How do containers and VMs run on one platform?
&lt;/h2&gt;

&lt;p&gt;The execution model decides what your operations team manages, which skills it needs, and which trade-offs it accepts.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Model&lt;/th&gt;
&lt;th&gt;How it works&lt;/th&gt;
&lt;th&gt;Strengths&lt;/th&gt;
&lt;th&gt;Trade-offs&lt;/th&gt;
&lt;th&gt;Examples&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;VMs inside Kubernetes (KubeVirt)&lt;/td&gt;
&lt;td&gt;KubeVirt runs a VM as a Kubernetes pod wrapping a KVM process. The VM gets a boot disk, virtual NIC, and CPU and memory allocation managed by the Kubernetes scheduler.&lt;/td&gt;
&lt;td&gt;One control plane for VMs and containers. Kubernetes networking, storage, and policy apply to both, with secondary VM networks needing their own policy. Declarative VM definitions stored in Git.&lt;/td&gt;
&lt;td&gt;Requires KVM-capable nodes. Live migration needs ReadWriteMany storage and is unavailable for VMs with passthrough devices. Automated load balancing and the backup and tooling ecosystem are less mature than vSphere’s.&lt;/td&gt;
&lt;td&gt;OpenShift Virtualization, SUSE Virtualization, Spectro Cloud Palette VMO, Mirantis k0rdent, VM Runtime on Google Distributed Cloud, Control Plane&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Hypervisor first with Kubernetes on top&lt;/td&gt;
&lt;td&gt;A traditional hypervisor (ESXi, AHV) runs VMs directly. Kubernetes clusters run as VMs on that hypervisor; VCF provisions them through the vSphere Supervisor, and NKP provisions them through its own Cluster API management cluster, which also targets public clouds.&lt;/td&gt;
&lt;td&gt;Mature VM feature set: live migration, snapshots, HA, GPU passthrough, and broad OS support. Familiar to virtualization teams.&lt;/td&gt;
&lt;td&gt;Two layers to operate: the hypervisor stack and the Kubernetes clusters on top. Tighter vendor coupling.&lt;/td&gt;
&lt;td&gt;VMware Cloud Foundation, Nutanix Cloud Platform with NKP&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;One management console over separate systems&lt;/td&gt;
&lt;td&gt;A management platform connects to existing hypervisors, cloud providers, and Kubernetes clusters, presenting a unified dashboard and policy engine without changing how VMs or containers execute.&lt;/td&gt;
&lt;td&gt;No re-platforming required. Works with whatever you already run. Fast to deploy.&lt;/td&gt;
&lt;td&gt;No runtime unification. Policies and networking remain siloed at the infrastructure layer. Depth of integration varies by connector.&lt;/td&gt;
&lt;td&gt;HPE Morpheus&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;The KubeVirt project extends Kubernetes to run VMs as native resources. It runs a virtual machine monitor inside a pod and boots a guest OS from a persistent volume. From Kubernetes’ perspective, the VM is another workload with CPU requests, memory limits, and network policies.&lt;/p&gt;

&lt;p&gt;The hypervisor-first model remains preferable when VM feature maturity is non-negotiable. VMware’s ESX/ESXi line (since 2001) and AHV (since 2015) bring years of management tooling for live migration, storage integration, and hardware certification, while KubeVirt uses the KVM hypervisor with a younger management layer. Teams that depend on those features and do not plan to containerize most workloads may find more stability here.&lt;/p&gt;

&lt;p&gt;The management-console model suits organizations that cannot or do not want to change their runtime layer. HPE Morpheus connects to VMware, Nutanix, Hyper-V, AWS, Azure, Google Cloud, Oracle Cloud, and Kubernetes clusters, providing visibility and governance without migrating a single VM. HPE also bundles its KVM-based VM Essentials hypervisor for teams that want to leave VMware.&lt;/p&gt;

&lt;h2&gt;
  
  
  What do VMs need from a public cloud?
&lt;/h2&gt;

&lt;p&gt;Running VMs on Kubernetes in a public cloud requires hardware virtualization support at the host level. KubeVirt relies on KVM, which in turn requires access to CPU virtualization extensions (Intel VT-x or AMD-V). Public cloud instances are themselves VMs, so running KVM inside them requires either bare-metal instances or instances that allow nested virtualization.&lt;/p&gt;

&lt;p&gt;Bare-metal instances are available on AWS (.metal sizes such as m5.metal and c5.metal), Google Cloud (C3, C4, and other metal machine types), and OCI (bare-metal shapes). Azure does not offer general-purpose bare-metal instances, so KubeVirt on Azure relies on nested virtualization; OpenShift Virtualization on ARO, for example, runs on supported Dsv5 and Esv5 VMs. Bare-metal instances give direct hardware access and full KVM support, but they come only in large sizes and not every region carries them.&lt;/p&gt;

&lt;p&gt;Nested virtualization is available on Google Cloud for most Intel-based machine series, on AWS for 7th- and 8th-generation Intel instances such as M8i, C8i, and R8i, and on Azure for sizes such as Dsv5 and Esv5. It adds overhead that is most visible on I/O-heavy and interrupt-heavy workloads, and some vendors support it only for limited production use.&lt;/p&gt;

&lt;p&gt;For hypervisor-first platforms, the cloud providers offer dedicated VMware and Nutanix environments. VMware Cloud on AWS, Azure VMware Solution, and Google Cloud VMware Engine provide ESXi hosts managed by the cloud provider. Nutanix Cloud Clusters run on AWS, Azure, Google Cloud, and OVHcloud bare-metal infrastructure. These services eliminate the nested-virtualization question but come with their own pricing and availability constraints.&lt;/p&gt;

&lt;p&gt;Before selecting a KubeVirt-based platform for public cloud VMs, confirm that your target cloud regions offer the instance types you need and that the cost fits your budget. On-premises deployments sidestep this entirely because you control the hardware.&lt;/p&gt;

&lt;h2&gt;
  
  
  How do you move VMs onto a container platform?
&lt;/h2&gt;

&lt;p&gt;Migrating existing VMs onto a Kubernetes-based platform involves converting disk images, validating guest OS compatibility, and reconfiguring networking and storage.&lt;/p&gt;

&lt;p&gt;VM disk images come in three common formats. VMDK is the VMware standard. qcow2 is used by KVM and QEMU. VHD and VHDX are Microsoft Hyper-V formats. KubeVirt’s Containerized Data Importer (CDI) can pull images over HTTP(S), from container registries, or from S3 or Google Cloud Storage and convert them into persistent volumes that back a VM workload.&lt;/p&gt;

&lt;p&gt;Live migration requires the VM’s disks on ReadWriteMany persistent volumes, ideally in block mode, from a CSI driver such as Ceph RBD, Portworx, or NetApp Trident; VMs on local or ReadWriteOnce storage can restart on another node but cannot live-migrate. By default a KubeVirt VM sits behind the pod network through NAT, so its reachable IP changes when it restarts elsewhere; VMs that must keep existing IPs or VLANs attach through Multus to a bridge or OVN-Kubernetes localnet secondary network.&lt;/p&gt;

&lt;p&gt;Red Hat provides the &lt;a href="https://docs.redhat.com/en/documentation/migration_toolkit_for_virtualization/" rel="noopener noreferrer"&gt;Migration Toolkit for Virtualization&lt;/a&gt; (MTV), which pulls VMs from VMware vSphere, Hyper-V, OpenStack, Red Hat Virtualization, OVA, and AWS EC2, maps networks and storage, converts guests with VirtIO drivers, and creates KubeVirt VM definitions in OpenShift. Nutanix offers Nutanix Move for migrating VMs from VMware to AHV. For other platforms, the workflow typically involves exporting the disk, converting the guest with virt-v2v so it boots on VirtIO devices, importing it with CDI, and defining the VM as a Kubernetes custom resource.&lt;/p&gt;

&lt;p&gt;Not every VM should stay a VM. Applications that are stateless, horizontally scalable, or already packaged as containers are better served by containerizing them during migration. The &lt;a href="https://controlplane.com/blog/post/modernize-vm-application-kubernetes-multi-cloud?utm_source=devto&amp;amp;utm_medium=syndication&amp;amp;utm_campaign=platforms-run-containers-and-vms-across-clouds" rel="noopener noreferrer"&gt;VM-to-Kubernetes modernization guide&lt;/a&gt; walks through the decision framework for when to modernize a VM into containers and when to keep it running as a VM workload.&lt;/p&gt;

&lt;p&gt;Key steps in any VM migration:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Export the VM disk image in VMDK, qcow2, or VHD format, or let a tool such as MTV pull it directly from vCenter.&lt;/li&gt;
&lt;li&gt;Upload or stream the image to the target platform using CDI, MTV, or the platform’s import tool.&lt;/li&gt;
&lt;li&gt;Map source networks and storage to Kubernetes networking (Multus, OVN-Kubernetes) and persistent volume classes.&lt;/li&gt;
&lt;li&gt;Validate guest OS drivers, cloud-init or sysprep configuration, and boot behavior.&lt;/li&gt;
&lt;li&gt;Test live migration if your workload requires it. KubeVirt migrates a VM only when its disks are on ReadWriteMany storage, it uses no passthrough devices, and another node offers a compatible CPU model.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Which questions decide the choice?
&lt;/h2&gt;

&lt;p&gt;Before committing to a platform, run through these questions with your infrastructure, security, and application teams.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Question&lt;/th&gt;
&lt;th&gt;Why it matters&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Do your VMs need live migration?&lt;/td&gt;
&lt;td&gt;KubeVirt supports live migration but requires ReadWriteMany storage (block mode preferred) and CPU-compatible nodes. Hypervisor-first platforms handle this natively. If live migration is critical, verify the platform’s support and test it in your environment.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Which hypervisor features do you depend on (DRS, snapshots, GPU passthrough, backup integrations)?&lt;/td&gt;
&lt;td&gt;KubeVirt covers live migration, snapshots, and GPU passthrough, but automated balancing and backup integrations vary by platform. Audit current feature usage before migrating. Windows Server VMs also need licenses for every node they can run on.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Can your target clouds provide bare metal or nested virtualization?&lt;/td&gt;
&lt;td&gt;KubeVirt needs KVM-capable nodes. If your preferred cloud regions lack bare-metal or nested-virt instances, you cannot run VMs there. Check availability and pricing early.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;How do VM images move in (VMDK, qcow2, VHD conversion)?&lt;/td&gt;
&lt;td&gt;Image format compatibility and conversion tooling vary by platform. Confirm that your disk formats are supported and that the import process handles your image sizes within acceptable timeframes.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;How are networking and storage shared between VMs and containers?&lt;/td&gt;
&lt;td&gt;Unified networking (CNI plugins, Multus for multiple interfaces) and storage (CSI drivers, persistent volumes) simplify operations but introduce new abstractions your team must learn.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Who operates the platform after migration?&lt;/td&gt;
&lt;td&gt;A KubeVirt-based platform requires Kubernetes expertise. A hypervisor-first platform requires traditional virtualization skills. A management-console approach requires familiarity with the console’s API and policy model. Match the platform to your team’s skills or plan for training.&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h2&gt;
  
  
  How Control Plane fits
&lt;/h2&gt;

&lt;p&gt;Control Plane is the unbreakable platform for running production workloads. It runs serverless, standard, stateful, and cron workloads natively on AWS, GCP, Azure, and Oracle Cloud Infrastructure (OCI), and VM workloads on locations joined through Control Plane’s Managed Kubernetes.&lt;/p&gt;

&lt;p&gt;VM workloads are a Control Plane workload type that runs full virtual machines with boot disks, persistence, cloud-init, and SSH, using KubeVirt on Managed Kubernetes locations. They need KVM-capable nodes labeled for VMs, such as AWS bare-metal instances, AWS 8th-generation Intel instances with nested virtualization, or your own KVM hosts. VM images in qcow2, raw, VMDK, VHD/VHDX, VDI, or ISO format can be imported over HTTP(S), where Control Plane converts them to the boot disk’s native format, or packaged as a container disk image in a registry.&lt;/p&gt;

&lt;p&gt;VM workloads do not run in Control Plane-managed cloud regions. Containers run in those regions and in Managed Kubernetes locations. A Global Virtual Cloud (GVC), which is Control Plane’s named set of locations, can include both, so VMs and containers share one control plane, one API, and one set of policies and secrets. VM workloads do not scale to zero automatically. Control Plane does not offer live migration yet, so a VM that moves to another node cold-boots there, with its disk state kept on attached volume sets. Secure Boot is not yet available for Control Plane VMs, so guests that require it, such as Windows 11, are not supported yet.&lt;/p&gt;

&lt;p&gt;Control Plane handles Day 2 operations for containers and VMs alike, including built-in observability, mTLS service mesh, and firewall rules. Containers also autoscale, while VM replica counts are set with minScale and maxScale. Control Plane is PCI DSS Level 1, SOC 2 Type II, HIPAA, and GDPR compliant.&lt;/p&gt;

&lt;p&gt;The &lt;a href="https://controlplane.com/blog/post/10-best-multi-cloud-management-platforms-in-2026?utm_source=devto&amp;amp;utm_medium=syndication&amp;amp;utm_campaign=platforms-run-containers-and-vms-across-clouds" rel="noopener noreferrer"&gt;multi-cloud management platforms roundup&lt;/a&gt; compares Control Plane with other multi-cloud platforms, and a separate guide covers &lt;a href="https://controlplane.com/blog/post/kubernetes-benefits-without-platform-team?utm_source=devto&amp;amp;utm_medium=syndication&amp;amp;utm_campaign=platforms-run-containers-and-vms-across-clouds" rel="noopener noreferrer"&gt;getting Kubernetes benefits without a platform team&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  FAQ
&lt;/h2&gt;

&lt;p&gt;These answers cover the questions teams ask when they combine VMs and containers.&lt;/p&gt;

&lt;h3&gt;
  
  
  Which platform runs both containers and full VMs across multiple clouds?
&lt;/h3&gt;

&lt;p&gt;Several platforms do this, using one of three architectures. Red Hat OpenShift Virtualization, SUSE Virtualization with Rancher, Spectro Cloud Palette VMO, Mirantis k0rdent, VM Runtime on Google Distributed Cloud, and Control Plane run VMs inside Kubernetes using KubeVirt. VMware Cloud Foundation and Nutanix Cloud Platform run a hypervisor with Kubernetes on top. HPE Morpheus manages separate VM and container systems from one console. The right choice depends on your execution model preference, target clouds, and operational skills.&lt;/p&gt;

&lt;h3&gt;
  
  
  What is KubeVirt?
&lt;/h3&gt;

&lt;p&gt;KubeVirt is a CNCF graduated project that extends Kubernetes to run virtual machines alongside containers. It creates a VM as a Kubernetes custom resource, backed by a KVM process running inside a pod. This lets teams use Kubernetes APIs, networking, storage, and policies for both VMs and containers on the same cluster.&lt;/p&gt;

&lt;h3&gt;
  
  
  Can Kubernetes run virtual machines?
&lt;/h3&gt;

&lt;p&gt;Yes. With KubeVirt installed on a Kubernetes cluster, VMs run as first-class Kubernetes objects. The cluster’s scheduler places VMs on nodes with KVM support, and persistent volumes provide boot disks and data storage. Multiple production platforms, including OpenShift Virtualization and VM Runtime on Google Distributed Cloud, rely on this approach.&lt;/p&gt;

&lt;h3&gt;
  
  
  Is OpenShift Virtualization a replacement for VMware?
&lt;/h3&gt;

&lt;p&gt;OpenShift Virtualization can replace VMware for many workloads, especially when an organization is already adopting Kubernetes. Red Hat’s Migration Toolkit for Virtualization automates the import of VMware VMs. OpenShift Virtualization supports live migration, snapshots, and Microsoft-certified Windows Server guests. VMware still leads in DRS-style automated balancing, storage policy integration, and the breadth of third-party backup and tooling. Evaluate your specific feature dependencies before migrating.&lt;/p&gt;

&lt;h3&gt;
  
  
  Do I need bare metal to run VMs on Kubernetes in the cloud?
&lt;/h3&gt;

&lt;p&gt;Not always, but you need KVM-capable nodes. AWS, Google Cloud, and OCI sell bare-metal instances; Azure does not, so Azure deployments use nested virtualization. Google Cloud, Azure, and AWS each support nested virtualization on specific instance types, though some vendors support it only for test or limited production use.&lt;/p&gt;

&lt;h3&gt;
  
  
  Can I run Windows VMs on Kubernetes?
&lt;/h3&gt;

&lt;p&gt;Yes. KubeVirt supports Windows guest operating systems, including Windows Server and Windows desktop editions. You need the appropriate Windows licenses, VirtIO drivers installed in the guest, and sufficient CPU and memory resources on the host nodes. Windows 11 guests need UEFI Secure Boot and a virtual TPM, which current KubeVirt releases provide. GPU passthrough for Windows VMs is supported on some platforms but should be tested in your environment.&lt;/p&gt;

&lt;h3&gt;
  
  
  How do I migrate VMware VMs to Kubernetes?
&lt;/h3&gt;

&lt;p&gt;Red Hat’s Migration Toolkit for Virtualization pulls disks directly from vCenter and handles discovery, network mapping, VirtIO driver conversion, warm migration, and VM creation for OpenShift. For other KubeVirt platforms, convert guests with virt-v2v, use the Containerized Data Importer to import the disks, and define VMs as Kubernetes custom resources. The &lt;a href="https://controlplane.com/blog/post/modernize-vm-application-kubernetes-multi-cloud?utm_source=devto&amp;amp;utm_medium=syndication&amp;amp;utm_campaign=platforms-run-containers-and-vms-across-clouds" rel="noopener noreferrer"&gt;VM-to-Kubernetes modernization guide&lt;/a&gt; covers when to keep a VM versus containerize the application.&lt;/p&gt;

&lt;h3&gt;
  
  
  How does Control Plane run VMs and containers?
&lt;/h3&gt;

&lt;p&gt;Control Plane runs containers as serverless, standard, stateful, and cron workloads in its managed regions on AWS, GCP, Azure, and Oracle Cloud Infrastructure (OCI). VM workloads run through KubeVirt on locations joined with Control Plane’s Managed Kubernetes, on nodes that support KVM. A Global Virtual Cloud (GVC), Control Plane’s named set of locations, can hold both kinds of location, so VMs and containers share one API, one policy set, and one set of secrets. Disk images are imported over HTTP(S) with format conversion, or as container disk images.&lt;/p&gt;

&lt;h3&gt;
  
  
  What is the main driver for evaluating these platforms in 2026?
&lt;/h3&gt;

&lt;p&gt;Changes to VMware’s licensing and pricing under Broadcom ownership are a major reason many enterprises are evaluating alternatives. Organizations that previously ran VMware across on-premises and cloud environments are now comparing KubeVirt-based platforms, alternative hypervisors, and management-console approaches to find a better fit for their cost structure, operational model, and multi-cloud strategy.&lt;/p&gt;

&lt;p&gt;To run containers and VMs across clouds under one API, &lt;a href="https://controlplane.com/requestdemo?utm_source=devto&amp;amp;utm_medium=syndication&amp;amp;utm_campaign=platforms-run-containers-and-vms-across-clouds" rel="noopener noreferrer"&gt;talk to the Control Plane team&lt;/a&gt; or &lt;a href="https://console.cpln.io/signup" rel="noopener noreferrer"&gt;sign up free&lt;/a&gt;.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Originally published on the &lt;a href="https://controlplane.com/blog/post/platforms-run-containers-and-vms-across-clouds?utm_source=devto&amp;amp;utm_medium=syndication&amp;amp;utm_campaign=platforms-run-containers-and-vms-across-clouds" rel="noopener noreferrer"&gt;Control Plane blog&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>kubernetes</category>
      <category>cloud</category>
      <category>devops</category>
      <category>virtualization</category>
    </item>
    <item>
      <title>Process-Local Deduplication Breaks the Moment You Add a Second Replica</title>
      <dc:creator>Zen Mesh Inc.</dc:creator>
      <pubDate>Tue, 17 Nov 2026 22:31:32 +0000</pubDate>
      <link>https://dev.to/zenmesh/process-local-deduplication-breaks-the-moment-you-add-a-second-replica-3h70</link>
      <guid>https://dev.to/zenmesh/process-local-deduplication-breaks-the-moment-you-add-a-second-replica-3h70</guid>
      <description>&lt;blockquote&gt;
&lt;p&gt;This is article 6 of 10 in &lt;a href="https://dev.to/zenmesh/when-kubernetes-primitives-arent-enough-10-production-guarantees-we-had-to-build-above-k8s-2f7c"&gt;Beyond Kubernetes Defaults&lt;/a&gt;. Read &lt;a href="https://dev.to/zenmesh/a-running-pod-is-not-an-admitted-workload-3fen"&gt;article 5: A Running Pod Is Not an Admitted Workload&lt;/a&gt; first.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Single-process correctness can hide distributed-system bugs. Replay protection is a particularly clear example.&lt;/p&gt;

&lt;h2&gt;
  
  
  One replica, then two
&lt;/h2&gt;

&lt;p&gt;A signed request arrives with a timestamp and a nonce. The application verifies the signature and records the nonce so it cannot be accepted twice. With one process and local state, this can look correct.&lt;/p&gt;

&lt;p&gt;Now run two replicas behind a Kubernetes Service. The first request lands on replica A, which records nonce N locally. A replay lands on B, which has never seen N. B accepts the same signed request.&lt;/p&gt;

&lt;p&gt;A Deployment or Service does not turn local security state into shared state. Scaling is not state synchronization.&lt;/p&gt;

&lt;h2&gt;
  
  
  Sticky routing is not a security boundary
&lt;/h2&gt;

&lt;p&gt;Consistent hashing or sticky sessions can reduce the chance of a replay reaching another replica. But Pods restart, pools resize and endpoints change. If membership movement makes a consumed nonce fresh again, routing affinity reduces probability; it does not enforce the guarantee.&lt;/p&gt;

&lt;h2&gt;
  
  
  Define the invariant
&lt;/h2&gt;

&lt;p&gt;After the first successful use of a nonce, every later use inside the replay window must be denied, regardless of which live replica receives it.&lt;/p&gt;

&lt;p&gt;A shared store, safely replicated state, or correctly managed partition ownership may help, but each design needs explicit answers about:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Scope:&lt;/strong&gt; include the appropriate tenant or source in the replay key.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Atomicity:&lt;/strong&gt; checking and recording must be one atomic operation; two replicas must not both accept the same nonce.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Lifetime:&lt;/strong&gt; retain the record for the full replay window, accounting for clock skew and membership changes.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Failure:&lt;/strong&gt; decide what happens when the replay authority is unavailable. For security-sensitive signed ingress, a retryable refusal is often safer than silently accepting without the check.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Acknowledgement has a similar boundary
&lt;/h2&gt;

&lt;p&gt;If a service returns HTTP 200 after putting an event only in process memory, a crash can lose the event after the sender believes it was accepted. A durable acknowledgement should correspond to the durability guarantee the service actually offers.&lt;/p&gt;

&lt;h2&gt;
  
  
  Test the seams
&lt;/h2&gt;

&lt;p&gt;A useful HA test is not just killing a Pod and checking that another stays up:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Send a signed request with nonce N and confirm acceptance.&lt;/li&gt;
&lt;li&gt;Replay N to a different replica and confirm rejection.&lt;/li&gt;
&lt;li&gt;Replace a replica and replay N again.&lt;/li&gt;
&lt;li&gt;Scale the pool up and down and repeat within the replay window.&lt;/li&gt;
&lt;li&gt;Make the replay authority unavailable and verify the documented failure behavior.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Also test the difference between recording durable acceptance and marking a downstream effect complete: suppressing a retry before an effect succeeds can lose an event.&lt;/p&gt;

&lt;h2&gt;
  
  
  This is not exactly-once delivery
&lt;/h2&gt;

&lt;p&gt;Fencing, replay protection and idempotency protect different boundaries. At-least-once transport with correctly scoped idempotent effects can be useful, but exactly-once claims need precise boundaries and evidence.&lt;/p&gt;

&lt;p&gt;A second replica is an availability feature and a correctness question: do your guarantees survive when state is distributed?&lt;/p&gt;

&lt;p&gt;Originally published on the &lt;a href="https://www.zen-mesh.io/blogs/kubernetes-ha-replay-dedup/" rel="noopener noreferrer"&gt;Zen Mesh blog&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>kubernetes</category>
      <category>devops</category>
      <category>architecture</category>
      <category>security</category>
    </item>
    <item>
      <title>AWS ECS Fargate GitHub Actions OIDC Deployment</title>
      <dc:creator>Muhammad Zeeshan</dc:creator>
      <pubDate>Tue, 17 Nov 2026 21:55:33 +0000</pubDate>
      <link>https://dev.to/muhammad_zeeshan_c5b0bf5b/aws-ecs-fargate-github-actions-oidc-deployment-50db</link>
      <guid>https://dev.to/muhammad_zeeshan_c5b0bf5b/aws-ecs-fargate-github-actions-oidc-deployment-50db</guid>
      <description>&lt;p&gt;Deploying to AWS ECS Fargate with GitHub Actions and OIDC enables secure, keyless authentication, streamlining CI/CD pipelines and enhancing security for containerized applications with temporary credentials.&lt;/p&gt;

&lt;h2&gt;
  
  
  Key Takeaways
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Use GitHub Actions for automated deployment to AWS ECS Fargate with OIDC.&lt;/li&gt;
&lt;li&gt;Implement OIDC for secure, keyless authentication in aws ecs fargate github actions oidc workflows.&lt;/li&gt;
&lt;li&gt;Configure AWS IAM roles for least privilege access in aws ecs fargate github actions oidc deployments.&lt;/li&gt;
&lt;li&gt;Monitor and log deployments for transparency and debugging in aws ecs fargate github actions oidc pipelines.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  How Does AWS ECS Fargate GitHub Actions OIDC Work?
&lt;/h2&gt;

&lt;p&gt;AWS ECS Fargate is a serverless compute engine for containers, while GitHub Actions is a CI/CD platform. By integrating them with OIDC, you can automate deployments without long-lived credentials. First, create an IAM role for your GitHub Actions workflow, then configure OIDC in your AWS account. For more information on OIDC, visit the &lt;a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_providers_oidc.html" rel="noopener noreferrer"&gt;AWS documentation&lt;/a&gt;.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="c"&gt;# Configure AWS CLI with OIDC&lt;/span&gt;
aws configure &lt;span class="nb"&gt;set&lt;/span&gt; credentials_url https://token.actions.githubusercontent.com
aws configure &lt;span class="nb"&gt;set&lt;/span&gt; role_arn arn:aws:iam::123456789012:role/GitHubActionsRole
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  What Are the Benefits of Using AWS ECS Fargate GitHub Actions OIDC?
&lt;/h2&gt;

&lt;p&gt;Using aws ecs fargate github actions oidc provides several benefits, including enhanced security, streamlined CI/CD pipelines, and automated deployment. By implementing OIDC, you can reduce the risk of credential exposure and improve the overall security of your containerized applications. For more information on GitHub Actions, visit the &lt;a href="https://docs.github.com/en/actions" rel="noopener noreferrer"&gt;GitHub Actions documentation&lt;/a&gt;.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight yaml"&gt;&lt;code&gt;&lt;span class="c1"&gt;# GitHub Actions workflow file
&lt;/span&gt;&lt;span class="na"&gt;name&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s"&gt;Deploy to AWS ECS Fargate with OIDC&lt;/span&gt;
&lt;span class="na"&gt;on&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
  &lt;span class="na"&gt;push&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
    &lt;span class="na"&gt;branches&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
      &lt;span class="p"&gt;-&lt;/span&gt; &lt;span class="s"&gt;main&lt;/span&gt;
&lt;span class="na"&gt;jobs&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
  &lt;span class="na"&gt;deploy&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
    &lt;span class="na"&gt;runs-on&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s"&gt;ubuntu-latest&lt;/span&gt;
    &lt;span class="na"&gt;steps&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
      &lt;span class="p"&gt;-&lt;/span&gt; &lt;span class="na"&gt;name&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s"&gt;Configure AWS Credentials&lt;/span&gt;
        &lt;span class="na"&gt;uses&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s"&gt;aws-actions/configure-aws-credentials@v1&lt;/span&gt;
        &lt;span class="na"&gt;with&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
          &lt;span class="na"&gt;aws-access-key-id&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s"&gt;${{ secrets.AWS_ACCESS_KEY_ID }}&lt;/span&gt;
          &lt;span class="na"&gt;aws-secret-access-key&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s"&gt;${{ secrets.AWS_SECRET_ACCESS_KEY }}&lt;/span&gt;
          &lt;span class="na"&gt;aws-region&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s1"&gt;'us-west-2'&lt;/span&gt;
      &lt;span class="p"&gt;-&lt;/span&gt; &lt;span class="na"&gt;name&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s"&gt;Deploy to ECS Fargate with OIDC&lt;/span&gt;
        &lt;span class="na"&gt;run&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;|&lt;/span&gt;
          &lt;span class="s"&gt;aws ecs create-cluster --cluster my-cluster&lt;/span&gt;
          &lt;span class="s"&gt;aws ecs create-service --cluster my-cluster --service my-service --task-definition my-task-def&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  How to Implement AWS ECS Fargate GitHub Actions OIDC for Secure Deployment?
&lt;/h2&gt;

&lt;p&gt;To implement aws ecs fargate github actions oidc, create an IAM role for your GitHub Actions workflow, then configure OIDC in your AWS account. Update your GitHub Actions workflow to use the OIDC credentials. For more information on AWS ECS Fargate, visit the &lt;a href="https://docs.aws.amazon.com/ecs/latest/userguide/what-is-fargate.html" rel="noopener noreferrer"&gt;AWS ECS Fargate documentation&lt;/a&gt;.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight python"&gt;&lt;code&gt;&lt;span class="c1"&gt;# Python script to create IAM role for GitHub Actions&lt;/span&gt;
&lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="n"&gt;boto3&lt;/span&gt;

&lt;span class="n"&gt;iam&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;boto3&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;client&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s1"&gt;'iam'&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;span class="n"&gt;response&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;iam&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;create_role&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;
    &lt;span class="nc"&gt;RoleName&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s1"&gt;'GitHubActionsRole'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="nc"&gt;AssumeRolePolicyDocument&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s2"&gt;'''{
        "Version": "2012-10-17",
        "Statement": [
            {
                "Effect": "Allow",
                "Principal": {
                    "FederatedIdentity": "arn:aws:iam::123456789012:oidc-provider/token.actions.githubusercontent.com"
                },
                "Action": "sts:AssumeRoleWithWebIdentity",
                "Condition": {
                    "StringLike": {
                        "token.actions.githubusercontent.com:sub": "repo:my-org/my-repo:*"
                    }
                }
            }
        ]
    }'''&lt;/span&gt;
&lt;span class="p"&gt;)&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  Why Is AWS ECS Fargate GitHub Actions OIDC Critical for Security?
&lt;/h2&gt;

&lt;p&gt;Using aws ecs fargate github actions oidc is critical for security because it provides secure, keyless authentication, reducing the risk of credential exposure. By implementing OIDC, you can improve the overall security of your containerized applications and streamline your CI/CD pipelines. For more information on security best practices, visit the &lt;a href="https://cheatsheetseries.owasp.org/" rel="noopener noreferrer"&gt;OWASP documentation&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  How to Monitor and Log AWS ECS Fargate GitHub Actions OIDC Deployments?
&lt;/h2&gt;

&lt;p&gt;To monitor and log aws ecs fargate github actions oidc deployments, use AWS CloudWatch and GitHub Actions logging features. These tools provide transparency and debugging capabilities, helping you to identify and resolve issues quickly. For more information on monitoring and logging, visit the &lt;a href="https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/" rel="noopener noreferrer"&gt;AWS CloudWatch documentation&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  What Are the Best Practices for Implementing AWS ECS Fargate GitHub Actions OIDC?
&lt;/h2&gt;

&lt;p&gt;To implement aws ecs fargate github actions oidc best practices, follow the AWS documentation guidelines for secure authentication and authorization. Use least privilege access and monitor your deployments regularly. For more information on best practices, visit the &lt;a href="https://docs.aws.amazon.com/security/" rel="noopener noreferrer"&gt;AWS Security documentation&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  How to Troubleshoot AWS ECS Fargate GitHub Actions OIDC Issues?
&lt;/h2&gt;

&lt;p&gt;To troubleshoot aws ecs fargate github actions oidc issues, check the AWS CloudWatch logs and GitHub Actions workflow logs. Identify the error message and follow the troubleshooting guide in the &lt;a href="https://docs.aws.amazon.com/ecs/latest/userguide/troubleshooting.html" rel="noopener noreferrer"&gt;AWS documentation&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Related Guides
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://blog.mzeeshan.online/posts/cloud-deployment-comparison/" rel="noopener noreferrer"&gt;Cloud Deployment Guide&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://blog.mzeeshan.online/posts/legacy-website-rewrite-guide/" rel="noopener noreferrer"&gt;Legacy Website Rewrite Guide&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://blog.mzeeshan.online/posts/php-password-hash-migration/" rel="noopener noreferrer"&gt;PHP Password Hash Migration&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Frequently Asked Questions
&lt;/h2&gt;

&lt;h3&gt;
  
  
  What is AWS ECS Fargate GitHub Actions OIDC?
&lt;/h3&gt;

&lt;p&gt;AWS ECS Fargate GitHub Actions OIDC is a secure method for deploying containerized applications with temporary credentials, enhancing security and streamlining CI/CD pipelines.&lt;/p&gt;

&lt;h3&gt;
  
  
  How do I configure AWS IAM roles for AWS ECS Fargate GitHub Actions OIDC?
&lt;/h3&gt;

&lt;p&gt;Create an IAM role for your GitHub Actions workflow, then configure OIDC in your AWS account, and update your workflow to use the OIDC credentials, following the AWS documentation guidelines.&lt;/p&gt;

&lt;h3&gt;
  
  
  What are the benefits of using AWS ECS Fargate GitHub Actions OIDC for deployment?
&lt;/h3&gt;

&lt;p&gt;The benefits include enhanced security, automated deployment, and streamlined CI/CD pipelines, reducing the risk of credential exposure and improving overall security with secure authentication.&lt;/p&gt;




&lt;h2&gt;
  
  
  Want to work together?
&lt;/h2&gt;

&lt;p&gt;I'm Muhammad Zeeshan, a DevOps &amp;amp; Agentic AI engineer. See my work and get in touch at &lt;a href="https://mzeeshan.online" rel="noopener noreferrer"&gt;mzeeshan.online&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Main site: &lt;a href="https://mzeeshan.online" rel="noopener noreferrer"&gt;https://mzeeshan.online&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;




&lt;p&gt;Originally published at &lt;a href="https://blog.mzeeshan.online/posts/aws-ecs-fargate-github-actions-oidc/" rel="noopener noreferrer"&gt;https://blog.mzeeshan.online/posts/aws-ecs-fargate-github-actions-oidc/&lt;/a&gt;. More about me: &lt;a href="https://mzeeshan.online" rel="noopener noreferrer"&gt;mzeeshan.online&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Main site: &lt;a href="https://mzeeshan.online" rel="noopener noreferrer"&gt;https://mzeeshan.online&lt;/a&gt;&lt;/p&gt;

</description>
      <category>devops</category>
      <category>cloud</category>
      <category>kubernetes</category>
      <category>ai</category>
    </item>
    <item>
      <title>Day 11: StatefulSets for Vector Databases — Deploying Milvus or Qdrant in Kubernetes</title>
      <dc:creator>Suresh Kumar Pallapothu</dc:creator>
      <pubDate>Tue, 17 Nov 2026 21:53:25 +0000</pubDate>
      <link>https://dev.to/suresh_kumar_de3920bedd1c/day-11-statefulsets-for-vector-databases-deploying-milvus-or-qdrant-in-kubernetes-3l4a</link>
      <guid>https://dev.to/suresh_kumar_de3920bedd1c/day-11-statefulsets-for-vector-databases-deploying-milvus-or-qdrant-in-kubernetes-3l4a</guid>
      <description>&lt;p&gt;A crashed stateless pod comes back with a random name and a new IP, and nobody minds. A database node that returns with a different identity can break &lt;strong&gt;cluster consensus&lt;/strong&gt; and force expensive re-sharding. A &lt;strong&gt;StatefulSet&lt;/strong&gt; fixes that with stable network identities, ordered operations and automatic per-pod storage.&lt;/p&gt;

&lt;h2&gt;
  
  
  Identity and storage
&lt;/h2&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Diagram:&lt;/strong&gt; FIG 1 · Each StatefulSet pod keeps a stable DNS name and its own PersistentVolumeClaim, and pods start in order. A restarted pod comes back as the same member. &lt;a href="https://sureshpallapothu.in/blog/ai-int-day-11-statefulsets-vector-db" rel="noopener noreferrer"&gt;See the animated version&lt;/a&gt;.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Each pod gets a predictable DNS name, such as &lt;code&gt;qdrant-0.qdrant-headless.ai-platform.svc.cluster.local&lt;/code&gt;, plus its own PVC. Pods start in order, &lt;code&gt;qdrant-0&lt;/code&gt; then &lt;code&gt;qdrant-1&lt;/code&gt;, and the name survives a restart.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why Deployments fail databases
&lt;/h2&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Diagram:&lt;/strong&gt; FIG 2 · Identity, storage and shutdown order all matter to a clustered database. StatefulSets handle each, and Deployments do not. &lt;a href="https://sureshpallapothu.in/blog/ai-int-day-11-statefulsets-vector-db" rel="noopener noreferrer"&gt;See the animated version&lt;/a&gt;.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Identity instability.&lt;/strong&gt; Random names and IPs after a restart force the cluster to re-sync large indexes.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Storage contention.&lt;/strong&gt; A Deployment shares one claim among its pods. A StatefulSet uses &lt;code&gt;volumeClaimTemplates&lt;/code&gt; to create a dedicated volume per replica.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Uncontrolled termination.&lt;/strong&gt; A Deployment can stop many pods at once. A StatefulSet stops them in strict reverse order, &lt;code&gt;qdrant-2&lt;/code&gt;, then &lt;code&gt;qdrant-1&lt;/code&gt;, then &lt;code&gt;qdrant-0&lt;/code&gt;, which helps the cluster keep quorum.&lt;/li&gt;
&lt;/ol&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Diagram:&lt;/strong&gt; FIG 3 · Pods start from zero upward and stop from the highest ordinal downward, which helps clustered databases keep quorum during restarts and updates. &lt;a href="https://sureshpallapothu.in/blog/ai-int-day-11-statefulsets-vector-db" rel="noopener noreferrer"&gt;See the animated version&lt;/a&gt;.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h2&gt;
  
  
  The manifest
&lt;/h2&gt;

&lt;p&gt;This runs Qdrant in clustered mode. Qdrant needs each new peer to know where to bootstrap from, so the first pod starts the cluster and the others join it.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight yaml"&gt;&lt;code&gt;&lt;span class="na"&gt;apiVersion&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s"&gt;v1&lt;/span&gt;
&lt;span class="na"&gt;kind&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s"&gt;Service&lt;/span&gt;
&lt;span class="na"&gt;metadata&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
  &lt;span class="na"&gt;name&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s"&gt;qdrant-headless&lt;/span&gt;
  &lt;span class="na"&gt;namespace&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s"&gt;ai-platform&lt;/span&gt;
&lt;span class="na"&gt;spec&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
  &lt;span class="na"&gt;clusterIP&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s"&gt;None&lt;/span&gt;
  &lt;span class="na"&gt;selector&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="s"&gt;app:&lt;/span&gt; &lt;span class="s"&gt;qdrant&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;
  &lt;span class="na"&gt;ports&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
    &lt;span class="p"&gt;-&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="s"&gt;name:&lt;/span&gt; &lt;span class="s"&gt;http&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s"&gt;port:&lt;/span&gt; &lt;span class="mi"&gt;6333&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;
    &lt;span class="p"&gt;-&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="s"&gt;name:&lt;/span&gt; &lt;span class="s"&gt;internal-p2p&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s"&gt;port:&lt;/span&gt; &lt;span class="mi"&gt;6335&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;
&lt;span class="nn"&gt;---
&lt;/span&gt;&lt;span class="na"&gt;apiVersion&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s"&gt;apps/v1&lt;/span&gt;
&lt;span class="na"&gt;kind&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s"&gt;StatefulSet&lt;/span&gt;
&lt;span class="na"&gt;metadata&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
  &lt;span class="na"&gt;name&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s"&gt;qdrant&lt;/span&gt;
  &lt;span class="na"&gt;namespace&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s"&gt;ai-platform&lt;/span&gt;
&lt;span class="na"&gt;spec&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
  &lt;span class="na"&gt;serviceName&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s"&gt;qdrant-headless&lt;/span&gt;
  &lt;span class="na"&gt;replicas&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mi"&gt;3&lt;/span&gt;
  &lt;span class="na"&gt;podManagementPolicy&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s"&gt;OrderedReady&lt;/span&gt;
  &lt;span class="na"&gt;selector&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
    &lt;span class="na"&gt;matchLabels&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="s"&gt;app:&lt;/span&gt; &lt;span class="s"&gt;qdrant&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;
  &lt;span class="na"&gt;template&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
    &lt;span class="na"&gt;metadata&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
      &lt;span class="na"&gt;labels&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="s"&gt;app:&lt;/span&gt; &lt;span class="s"&gt;qdrant&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;
    &lt;span class="na"&gt;spec&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
      &lt;span class="na"&gt;containers&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
        &lt;span class="p"&gt;-&lt;/span&gt; &lt;span class="na"&gt;name&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s"&gt;qdrant&lt;/span&gt;
          &lt;span class="na"&gt;image&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s"&gt;qdrant/qdrant:v1.9.0&lt;/span&gt;
          &lt;span class="na"&gt;env&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
            &lt;span class="p"&gt;-&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="s"&gt;name:&lt;/span&gt; &lt;span class="s"&gt;QDRANT__CLUSTER__ENABLED&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s"&gt;value:&lt;/span&gt; &lt;span class="s2"&gt;"true"&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;
            &lt;span class="p"&gt;-&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="s"&gt;name:&lt;/span&gt; &lt;span class="s"&gt;QDRANT__CLUSTER__P2P__PORT&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s"&gt;value:&lt;/span&gt; &lt;span class="s2"&gt;"6335"&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;
          &lt;span class="na"&gt;command&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s2"&gt;"/bin/sh"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s2"&gt;"-c"&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;
          &lt;span class="na"&gt;args&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
            &lt;span class="p"&gt;-&lt;/span&gt; &lt;span class="p"&gt;|&lt;/span&gt;
              &lt;span class="s"&gt;HOST="$(hostname).qdrant-headless"&lt;/span&gt;
              &lt;span class="s"&gt;if [ "$(hostname)" = "qdrant-0" ]; then&lt;/span&gt;
                &lt;span class="s"&gt;./qdrant --uri "http://${HOST}:6335"&lt;/span&gt;
              &lt;span class="s"&gt;else&lt;/span&gt;
                &lt;span class="s"&gt;./qdrant --bootstrap "http://qdrant-0.qdrant-headless:6335" --uri "http://${HOST}:6335"&lt;/span&gt;
              &lt;span class="s"&gt;fi&lt;/span&gt;
          &lt;span class="na"&gt;ports&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
            &lt;span class="p"&gt;-&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="s"&gt;name:&lt;/span&gt; &lt;span class="s"&gt;http&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s"&gt;containerPort:&lt;/span&gt; &lt;span class="mi"&gt;6333&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;
            &lt;span class="p"&gt;-&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="s"&gt;name:&lt;/span&gt; &lt;span class="s"&gt;p2p&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s"&gt;containerPort:&lt;/span&gt; &lt;span class="mi"&gt;6335&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;
          &lt;span class="na"&gt;resources&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
            &lt;span class="na"&gt;requests&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="s"&gt;cpu:&lt;/span&gt; &lt;span class="s2"&gt;"1000m"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s"&gt;memory:&lt;/span&gt; &lt;span class="s"&gt;2Gi&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;
            &lt;span class="na"&gt;limits&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;   &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="s"&gt;cpu:&lt;/span&gt; &lt;span class="s2"&gt;"2000m"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s"&gt;memory:&lt;/span&gt; &lt;span class="s"&gt;4Gi&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;
          &lt;span class="na"&gt;volumeMounts&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
            &lt;span class="p"&gt;-&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="s"&gt;name:&lt;/span&gt; &lt;span class="s"&gt;qdrant-data&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s"&gt;mountPath:&lt;/span&gt; &lt;span class="s"&gt;/qdrant/storage&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;
  &lt;span class="na"&gt;volumeClaimTemplates&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
    &lt;span class="p"&gt;-&lt;/span&gt; &lt;span class="na"&gt;metadata&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="s"&gt;name:&lt;/span&gt; &lt;span class="s"&gt;qdrant-data&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;
      &lt;span class="na"&gt;spec&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
        &lt;span class="na"&gt;accessModes&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s"&gt;ReadWriteOnce&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;
        &lt;span class="na"&gt;resources&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
          &lt;span class="na"&gt;requests&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="s"&gt;storage:&lt;/span&gt; &lt;span class="s"&gt;20Gi&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Check the bootstrap flags against the Qdrant version you run, because clustering options have changed between releases.&lt;/p&gt;

&lt;h2&gt;
  
  
  How many replicas?
&lt;/h2&gt;

&lt;p&gt;Raft-based clusters need a &lt;strong&gt;majority&lt;/strong&gt; of nodes to agree. One and two nodes tolerate &lt;strong&gt;no&lt;/strong&gt; failures, three tolerate one, and five tolerate two. Two replicas are fine for a lab, but for real fault tolerance run three.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Diagram:&lt;/strong&gt; FIG 4 · A Raft cluster needs a majority of nodes to agree. Three nodes tolerate one failure, five tolerate two, and two nodes tolerate none, so use at least three replicas when availability matters. &lt;a href="https://sureshpallapothu.in/blog/ai-int-day-11-statefulsets-vector-db" rel="noopener noreferrer"&gt;See the animated version&lt;/a&gt;.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Proper StatefulSet design protects your vector indexes through restarts and upgrades, and it gives the rest of the stack a database that behaves predictably.&lt;/p&gt;

&lt;h2&gt;
  
  
  Run it yourself
&lt;/h2&gt;

&lt;p&gt;This is the exact example from the video. Run against a real K3d cluster. A small nginx image stands in for Qdrant so three pods start quickly.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight yaml"&gt;&lt;code&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="s"&gt;apiVersion:&lt;/span&gt; &lt;span class="s"&gt;v1&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s"&gt;kind:&lt;/span&gt; &lt;span class="s"&gt;Service&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s"&gt;metadata:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="s"&gt;name:&lt;/span&gt; &lt;span class="s"&gt;qdrant-headless&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
 &lt;span class="na"&gt;spec&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="s"&gt;clusterIP:&lt;/span&gt; &lt;span class="s"&gt;None&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s"&gt;selector:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="s"&gt;app:&lt;/span&gt; &lt;span class="s"&gt;qdrant&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;
&lt;span class="nn"&gt;---
&lt;/span&gt;&lt;span class="na"&gt;apiVersion&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s"&gt;apps/v1&lt;/span&gt;
&lt;span class="na"&gt;kind&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s"&gt;StatefulSet&lt;/span&gt;
&lt;span class="na"&gt;metadata&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="s"&gt;name:&lt;/span&gt; &lt;span class="s"&gt;qdrant&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;
&lt;span class="na"&gt;spec&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
  &lt;span class="na"&gt;serviceName&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s"&gt;qdrant-headless&lt;/span&gt;
  &lt;span class="na"&gt;replicas&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mi"&gt;3&lt;/span&gt;
  &lt;span class="na"&gt;selector&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="s"&gt;matchLabels:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="s"&gt;app:&lt;/span&gt; &lt;span class="s"&gt;qdrant&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;
  &lt;span class="na"&gt;template&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
    &lt;span class="na"&gt;metadata&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="s"&gt;labels:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="s"&gt;app:&lt;/span&gt; &lt;span class="s"&gt;qdrant&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;
    &lt;span class="na"&gt;spec&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="s"&gt;containers:&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="s"&gt;name:&lt;/span&gt; &lt;span class="s"&gt;qdrant&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s"&gt;image:&lt;/span&gt; &lt;span class="s2"&gt;"nginx:1.27-alpine"&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;
  &lt;span class="na"&gt;volumeClaimTemplates&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
    &lt;span class="p"&gt;-&lt;/span&gt; &lt;span class="na"&gt;metadata&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="s"&gt;name:&lt;/span&gt; &lt;span class="s"&gt;data&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;
      &lt;span class="na"&gt;spec&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="s"&gt;accessModes:&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s"&gt;ReadWriteOnce&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
        &lt;span class="na"&gt;resources&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="s"&gt;requests:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="s"&gt;storage:&lt;/span&gt; &lt;span class="s"&gt;1Gi&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Run it:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;kubectl apply -f statefulset.yaml
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Output I got while recording the video:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;qdrant-0 Running
qdrant-1 Running
qdrant-2 Running
data-qdrant-0 Bound
data-qdrant-1 Bound
data-qdrant-2 Bound
headless clusterIP: None
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  Coming Up Next
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Day 12:&lt;/strong&gt; Auto-scaling AI inference with Horizontal Pod Autoscalers for spiky API traffic.&lt;/p&gt;

&lt;h1&gt;
  
  
  StatefulSet #VectorDatabase #Qdrant #Milvus #CloudNative #DataEngineering #SystemDesign
&lt;/h1&gt;




&lt;p&gt;&lt;em&gt;Originally published at &lt;a href="https://sureshpallapothu.in/blog/ai-int-day-11-statefulsets-vector-db" rel="noopener noreferrer"&gt;https://sureshpallapothu.in/blog/ai-int-day-11-statefulsets-vector-db&lt;/a&gt;, where this post includes animated diagrams.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>kubernetes</category>
      <category>statefulset</category>
      <category>aiintermediateseries</category>
    </item>
    <item>
      <title>A slow GPU isn't a broken GPU: grading GPUs per workload in Kubernetes (measured on real A10Gs)</title>
      <dc:creator>praveen9161</dc:creator>
      <pubDate>Tue, 17 Nov 2026 20:13:02 +0000</pubDate>
      <link>https://dev.to/praveen9161/a-slow-gpu-isnt-a-broken-gpu-grading-gpus-per-workload-in-kubernetes-measured-on-real-a10gs-4mij</link>
      <guid>https://dev.to/praveen9161/a-slow-gpu-isnt-a-broken-gpu-grading-gpus-per-workload-in-kubernetes-measured-on-real-a10gs-4mij</guid>
      <description>&lt;p&gt;GPU clusters treat a GPU as healthy or broken. Real GPUs also end up &lt;strong&gt;slow&lt;/strong&gt;: a lowered&lt;br&gt;
power limit, a clock lock, heat. That middle state is expensive in a specific way: in&lt;br&gt;
synchronous distributed training every step waits for the slowest GPU, so one slow GPU&lt;br&gt;
slows &lt;em&gt;every&lt;/em&gt; GPU in the job, and you pay for all of them.&lt;/p&gt;

&lt;p&gt;The usual answer is to remove the slow GPU. But "slow" depends on the work. So I built&lt;br&gt;
&lt;strong&gt;GPUFit&lt;/strong&gt;, an open-source tool that grades every GPU &lt;em&gt;per workload&lt;/em&gt; (training, fine-tuning,&lt;br&gt;
inference) and uses that grade for scheduling in Kubernetes: a degraded GPU is kept out of&lt;br&gt;
synchronous training and keeps serving inference.&lt;/p&gt;

&lt;p&gt;Everything below was measured on real NVIDIA GPUs on AWS. Total spend: about &lt;strong&gt;$8.50&lt;/strong&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  The same fault hurts workloads very differently
&lt;/h2&gt;

&lt;p&gt;One A10G, power limit lowered from its default 300 W, three runs each:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Power limit&lt;/th&gt;
&lt;th&gt;Heavy matrix multiply (training-like)&lt;/th&gt;
&lt;th&gt;Memory copy (inference-like)&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;250 W&lt;/td&gt;
&lt;td&gt;0.94&lt;/td&gt;
&lt;td&gt;1.00&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;150 W&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;0.68&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;1.00&lt;/strong&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;100 W&lt;/td&gt;
&lt;td&gt;0.35&lt;/td&gt;
&lt;td&gt;1.00&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;At 150 W the GPU lost a third of its speed for compute-heavy work and nothing for&lt;br&gt;
memory-bound work. A "healthy/unhealthy" flag can't express that. A per-workload grade can.&lt;/p&gt;

&lt;h2&gt;
  
  
  How GPUFit works
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;An &lt;strong&gt;agent&lt;/strong&gt; on each GPU node turns GPU health (from &lt;code&gt;nvidia-smi&lt;/code&gt;) into a score per
workload. Training uses the &lt;em&gt;weakest&lt;/em&gt; component, because one straggler sets the pace.&lt;/li&gt;
&lt;li&gt;A &lt;strong&gt;controller&lt;/strong&gt; moves a node with a GPU that's unfit for training into an &lt;strong&gt;inference
pool&lt;/strong&gt;, using Kubernetes &lt;strong&gt;DRA device taints&lt;/strong&gt; (Dynamic Resource Allocation, stable in
Kubernetes 1.37). Training claims don't tolerate the taint; inference claims do. No custom
scheduler, and it works with any DRA driver, including NVIDIA's.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Hysteresis&lt;/strong&gt;: a GPU must stay degraded for a while before it moves, and stay healthy for
longer before it comes back, so noisy GPUs don't flap.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Observe mode&lt;/strong&gt; (the default) changes nothing and reports what it &lt;em&gt;would&lt;/em&gt; do, plus
&lt;code&gt;kubectl gpufit report&lt;/code&gt;: training time on degraded GPUs and the estimated waste.
&lt;strong&gt;Enforce mode&lt;/strong&gt; applies it. Optional &lt;strong&gt;rescue&lt;/strong&gt; moves running training jobs that opted
in off a degraded GPU; they resume from their checkpoint.&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;kubectl gpufit why &amp;lt;pod&amp;gt;&lt;/code&gt; explains a Pending GPU pod. The scheduler says "cannot allocate
all claims" whether the cluster is busy or the GPUs are unfit; this tells them apart.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Install: &lt;code&gt;helm install gpufit oci://ghcr.io/praveen9161/charts/gpufit --version 0.1.0 -n gpufit --create-namespace&lt;/code&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Result 1: -25% cost per useful GPU-hour
&lt;/h2&gt;

&lt;p&gt;Two A10Gs, k3s, NVIDIA's DRA driver. GPU B's power limit cut to 150 W.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Without GPUFit&lt;/strong&gt;, Kubernetes put a 2-GPU training job on A+B. It ran at &lt;strong&gt;0.84&lt;/strong&gt; of its
healthy speed: one slow GPU dragged the healthy one down.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;With GPUFit&lt;/strong&gt;, B moved to the inference pool. Training got the healthy GPU (1.00) and
B served inference at &lt;strong&gt;0.98&lt;/strong&gt; of a healthy GPU.&lt;/li&gt;
&lt;/ul&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;&lt;/th&gt;
&lt;th&gt;Useful work (healthy-GPU equivalents)&lt;/th&gt;
&lt;th&gt;Efficiency&lt;/th&gt;
&lt;th&gt;$ per useful GPU-hour&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Without GPUFit&lt;/td&gt;
&lt;td&gt;1.49&lt;/td&gt;
&lt;td&gt;74%&lt;/td&gt;
&lt;td&gt;$1.35&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;With GPUFit&lt;/td&gt;
&lt;td&gt;1.98&lt;/td&gt;
&lt;td&gt;99%&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;$1.02&lt;/strong&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;The honest caveat: with only two GPUs and no spare, the training job itself got slower&lt;br&gt;
(one GPU instead of two). The gain is that almost no paid GPU time was wasted. In a bigger&lt;br&gt;
cluster, training would get a healthy spare.&lt;/p&gt;

&lt;h2&gt;
  
  
  Result 2: rescuing a job that's already running
&lt;/h2&gt;

&lt;p&gt;Four A10Gs, GPUFit installed with its Helm chart. A 2-GPU training job (400 steps,&lt;br&gt;
checkpoint every 50); at step 100 one of its GPUs drops to 150 W.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Run&lt;/th&gt;
&lt;th&gt;Job time&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Healthy&lt;/td&gt;
&lt;td&gt;901 s&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Degraded, GPUFit in observe mode (job stays as a straggler)&lt;/td&gt;
&lt;td&gt;1001 s&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Degraded, GPUFit in enforce + rescue mode&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;987 s&lt;/strong&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;What the rescue did: 32 s after the power cut the node left the training pool; 36 s later&lt;br&gt;
(a 30 s grace period) GPUFit evicted the job; 22 s later both pods ran again on healthy GPUs&lt;br&gt;
and resumed from step 100.&lt;/p&gt;

&lt;p&gt;A 14-second win is small, and that's the interesting part. The straggler lost 13% of every&lt;br&gt;
remaining second; the rescue cost about 86 s, fixed. So rescue pays off once more than&lt;br&gt;
&lt;strong&gt;about 10 minutes&lt;/strong&gt; of work remain after the GPU degrades (an estimate from these&lt;br&gt;
measurements; about 16 minutes with production timers). Real training jobs run for hours.&lt;/p&gt;

&lt;h2&gt;
  
  
  What didn't work (yet)
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;The waste estimate is too pessimistic.&lt;/strong&gt; GPUFit's report estimates speed from the score
(score 50 = half speed). The real job ran at 0.87, so the estimate was &lt;strong&gt;3.8x&lt;/strong&gt; the measured
waste. Scores from hardware settings are a trigger, not a speedometer.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Small scale.&lt;/strong&gt; 2-4 GPUs, synthetic workloads, one kind of induced fault. A straggler slows
every GPU in its job, so the loss grows with job size; I haven't measured beyond 2-GPU jobs.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Network slowdowns aren't covered.&lt;/strong&gt; In the FALCON study (Alibaba, HKUST),
network slowdowns were 7.2x more common than GPU compute slowdowns.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Things that bit me
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;k3s' default pod network (10.42.0.0/16) overlapped my VPC (also 10.42.0.0/16). Nodes
silently routed each other's real addresses into the pod network.&lt;/li&gt;
&lt;li&gt;NVIDIA's DRA kubelet plugin only runs on nodes labelled &lt;code&gt;nvidia.com/gpu.present=true&lt;/code&gt;,
normally set by GPU feature discovery, which I hadn't installed: zero GPUs published.&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;helm uninstall&lt;/code&gt; left my taints behind, so training would have avoided those GPUs forever.
The fix (a pre-delete hook) first failed too: the controller was still running and
re-applied the taint one second after cleanup. Now the hook stops the controller first.&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;helm upgrade --reuse-values&lt;/code&gt; turns a &lt;code&gt;null&lt;/code&gt; value override into an empty string. My agent
quietly stopped scheduling on the test cluster.&lt;/li&gt;
&lt;li&gt;An evicted pod still reports &lt;code&gt;Running&lt;/code&gt; while it shuts down. My first rescue timeline said
"running again after 0 s".&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  How this compares
&lt;/h2&gt;

&lt;p&gt;Others detect slow GPUs well: NVIDIA's nvidia-resiliency-ext scores each GPU inside&lt;br&gt;
training, ByteDance's MegaScale and FALCON (Alibaba, HKUST) find stragglers across thousands of GPUs,&lt;br&gt;
NVIDIA's DRA driver taints GPUs with hard faults, and HeaRank (KDD 2026) steers GPUs likely&lt;br&gt;
to fail toward interruption-tolerant work. What I couldn't find in the open is the next step:&lt;br&gt;
grading by measured &lt;em&gt;performance per workload&lt;/em&gt; and keeping the slow GPUs earning on&lt;br&gt;
inference through standard Kubernetes DRA, with the cost effect measured.&lt;/p&gt;

&lt;h2&gt;
  
  
  What's next
&lt;/h2&gt;

&lt;p&gt;Use the real per-GPU speed from the training jobs (via NVIDIA's own tooling) instead of&lt;br&gt;
estimating it, grade GPUs separately for LLM prefill and decode so degraded GPUs can feed&lt;br&gt;
decode pools, catch network slowdowns, and measure at 8-32 GPUs.&lt;/p&gt;

&lt;p&gt;Code, every raw result, and a cost calculator for your own fleet:&lt;br&gt;
&lt;strong&gt;&lt;a href="https://github.com/praveen9161/gpufit" rel="noopener noreferrer"&gt;https://github.com/praveen9161/gpufit&lt;/a&gt;&lt;/strong&gt; (Apache-2.0).&lt;br&gt;
Calculator: &lt;a href="https://praveen9161.github.io/gpufit/calculator/" rel="noopener noreferrer"&gt;https://praveen9161.github.io/gpufit/calculator/&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Feedback welcome, especially if you run GPU fleets: how often do your GPUs end up slow but not broken?&lt;br&gt;
&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fxsks7eun515v4d057d6g.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fxsks7eun515v4d057d6g.png" alt=" " width="800" height="450"&gt;&lt;/a&gt;&lt;/p&gt;

</description>
      <category>kubernetes</category>
      <category>gpu</category>
      <category>mlops</category>
      <category>devops</category>
    </item>
  </channel>
</rss>
