<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Configmaps on Apurv Kiri | Tech Notes</title>
    <link>https://apurv.me/tags/configmaps/</link>
    <description>Recent content in Configmaps on Apurv Kiri | Tech Notes</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-gb</language>
    <lastBuildDate>Thu, 06 Mar 2025 01:55:15 +0530</lastBuildDate><atom:link href="https://apurv.me/tags/configmaps/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Kubernetes - Automating ConfigMap and Secret Reloads with Reloader</title>
      <link>https://apurv.me/posts/kubernetes-automating-configmap-secret-reloads-with-reloader/</link>
      <pubDate>Thu, 06 Mar 2025 01:55:15 +0530</pubDate>
      
      <guid>https://apurv.me/posts/kubernetes-automating-configmap-secret-reloads-with-reloader/</guid>
      
      <description>&lt;hr&gt;
&lt;p&gt;This post is part of our ongoing series of posts for Kubernetes. In this post, we will explore how to automate the reloading of ConfigMaps and Secrets in your Kubernetes clusters using Reloader, a powerful tool designed to streamline application configuration updates without manual intervention.&lt;/p&gt;
&lt;p&gt;When working with applications that rely on configuration data or sensitive information stored in ConfigMaps and Secrets, manually restarting pods to apply changes can be tedious, error-prone, and disruptive to service availability. Reloader elegantly solves this problem by automatically detecting configuration changes and triggering rolling updates for the associated deployments, ensuring your applications always run with the latest configurations while maintaining high availability.&lt;/p&gt;</description>
      
    </item>
    
  </channel>
</rss>
