<?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: Gaberial Sofie</title>
    <description>The latest articles on DEV Community by Gaberial Sofie (@gaberialsofie).</description>
    <link>https://dev.to/gaberialsofie</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4037853%2F9db7fbce-a297-4e2c-b4ff-82ea86d94637.png</url>
      <title>DEV Community: Gaberial Sofie</title>
      <link>https://dev.to/gaberialsofie</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/gaberialsofie"/>
    <language>en</language>
    <item>
      <title>Local Kubernetes Dev — Part 3: Tooling overview — who does what</title>
      <dc:creator>Gaberial Sofie</dc:creator>
      <pubDate>Tue, 28 Jul 2026 20:22:41 +0000</pubDate>
      <link>https://dev.to/gaberialsofie/local-kubernetes-dev-part-3-tooling-overview-who-does-what-3an1</link>
      <guid>https://dev.to/gaberialsofie/local-kubernetes-dev-part-3-tooling-overview-who-does-what-3an1</guid>
      <description>&lt;p&gt;k3d, kind, minikube, Helm, Kustomize, Tilt, Skaffold, DevSpace, Telepresence, k9s... it reads like an incantation, and it's easy to drown in.&lt;/p&gt;

&lt;p&gt;If you've ever opened the CNCF landscape and felt you had to master all of it at once — relax. In reality each tool owns its own little shelf, and once you sort them out, the picture gets simple. Part three of the local Kubernetes series is a map of the 2025–2026 ecosystem: who does what, and why you probably only need two tools from this list.&lt;/p&gt;

&lt;p&gt;I lay it all out: Docker and kubectl are the foundation (cluster nodes are just Docker containers); local clusters k3d / kind / minikube / Docker Desktop / Rancher Desktop; Helm vs Kustomize (templating package manager vs overlay patches); inner-loop accelerators Tilt / Skaffold / DevSpace; the separate "remote" approach Telepresence / mirrord / Gefyra; and k9s as a visual kubectl. And I honestly explain why, for the end-to-end myapp example (FastAPI + PostgreSQL), the series picked k3d + Tilt: a real Kubernetes API with a fast start plus Live Update that squeezes the loop from minutes to seconds.&lt;/p&gt;

&lt;p&gt;Opinionated, but honestly so: "we chose X for these reasons," not "X is the best." &lt;a href="https://dorokhovich.com/blog/local-k8s-tooling-overview?utm_source=devto&amp;amp;utm_medium=syndication&amp;amp;utm_campaign=local-k8s-tooling-overview" rel="noopener noreferrer"&gt;https://dorokhovich.com/blog/local-k8s-tooling-overview?utm_source=devto&amp;amp;utm_medium=syndication&amp;amp;utm_campaign=local-k8s-tooling-overview&lt;/a&gt;&lt;/p&gt;

</description>
      <category>devops</category>
      <category>docker</category>
      <category>kubernetes</category>
    </item>
  </channel>
</rss>
