<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Secrets on Apurv Kiri | Tech Notes</title>
    <link>https://apurv.me/tags/secrets/</link>
    <description>Recent content in Secrets 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/secrets/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>
    
    <item>
      <title>Kubernetes - Replicate Secrets with Reflector</title>
      <link>https://apurv.me/posts/kubernetes-replicate-secrets-with-reflector/</link>
      <pubDate>Wed, 05 Mar 2025 01:55:15 +0530</pubDate>
      
      <guid>https://apurv.me/posts/kubernetes-replicate-secrets-with-reflector/</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 dive into replicating secrets across namespaces using Reflector, a powerful tool for ensuring consistency and security in your Kubernetes environment.&lt;/p&gt;
&lt;p&gt;By default, Kubernetes secrets are scoped to individual namespaces. However, there are common use cases where sensitive information, such as API tokens, database credentials, or container registry credentials, needs to be shared across multiple namespaces. Manually managing these secrets can be error-prone and time-consuming.&lt;/p&gt;</description>
      
    </item>
    
  </channel>
</rss>
