<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Kubernetes on blanpa</title><link>https://blanpa.github.io/tags/kubernetes/</link><description>Recent content in Kubernetes on blanpa</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>© 2026 blanpa</copyright><lastBuildDate>Sat, 18 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blanpa.github.io/tags/kubernetes/index.xml" rel="self" type="application/rss+xml"/><item><title>Docker vs K3s on the Shop Floor — Edge Deployment Strategies</title><link>https://blanpa.github.io/blog/docker-vs-k3s-edge-deployment/</link><pubDate>Sat, 18 Apr 2026 00:00:00 +0000</pubDate><guid>https://blanpa.github.io/blog/docker-vs-k3s-edge-deployment/</guid><description>&lt;p>Containers on the shop floor used to be a hard sell. &amp;ldquo;Why not just install the software directly?&amp;rdquo; plant engineers would ask. After rolling back a failed manual update at 2 AM for the third time, the answer becomes obvious: reproducibility, isolation, and the ability to roll back in seconds instead of hours.&lt;/p>
&lt;p>The real question isn&amp;rsquo;t &lt;em>whether&lt;/em> to use containers in industrial environments — it&amp;rsquo;s whether to use &lt;strong>Docker Compose&lt;/strong> or go all in with &lt;strong>K3s&lt;/strong> (lightweight Kubernetes). I&amp;rsquo;ve deployed both. Here&amp;rsquo;s when each makes sense.&lt;/p></description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://blanpa.github.io/blog/docker-vs-k3s-edge-deployment/featured.png"/></item></channel></rss>