<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Configmap on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/configmap/</link>
    <description>Recent content in Configmap on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 14 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/configmap/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Kubernetes ConfigMap Auto-Reload Tools: Stakater Reloader vs Configmap-Reloader vs K8s ConfigMap Watcher (2026)</title>
      <link>https://www.pistack.xyz/posts/2026-05-14-k8s-configmap-auto-reload-tools-stakater-reloader-vs-configmap-reloader-vs-watcher-guide/</link>
      <pubDate>Thu, 14 May 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-05-14-k8s-configmap-auto-reload-tools-stakater-reloader-vs-configmap-reloader-vs-watcher-guide/</guid>
      <description>&lt;p&gt;When you update a ConfigMap or Secret in Kubernetes, running pods don&amp;rsquo;t automatically pick up the changes unless the application explicitly re-reads the files or the pod is restarted. This is one of the most common pain points for Kubernetes administrators managing configuration-driven workloads. Manual pod restarts work for a handful of deployments, but they don&amp;rsquo;t scale across dozens of microservices. That&amp;rsquo;s where ConfigMap auto-reload tools come in — Kubernetes controllers that watch for configuration changes and trigger rolling updates automatically.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
