<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Reflector on Apurv Kiri | Tech Notes</title>
    <link>https://apurv.me/tags/reflector/</link>
    <description>Recent content in Reflector on Apurv Kiri | Tech Notes</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-gb</language>
    <lastBuildDate>Wed, 05 Mar 2025 01:55:15 +0530</lastBuildDate><atom:link href="https://apurv.me/tags/reflector/index.xml" rel="self" type="application/rss+xml" />
    <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>
