<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Externaldns on Apurv Kiri | Tech Notes</title>
    <link>https://apurv.me/tags/externaldns/</link>
    <description>Recent content in Externaldns on Apurv Kiri | Tech Notes</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-gb</language>
    <lastBuildDate>Fri, 28 Feb 2025 01:55:15 +0530</lastBuildDate><atom:link href="https://apurv.me/tags/externaldns/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Kubernetes - Setup External DNS</title>
      <link>https://apurv.me/posts/kubernetes-setup-external-dns/</link>
      <pubDate>Fri, 28 Feb 2025 01:55:15 +0530</pubDate>
      
      <guid>https://apurv.me/posts/kubernetes-setup-external-dns/</guid>
      
      <description>&lt;hr&gt;
&lt;p&gt;This post is part of our ongoing series of posts for Kubernetes. In this post we are focusing on setting up External DNS, a critical component for automating DNS record management. Although we are working on a local Kubernetes cluster, we have implemented prerequisites in &lt;a href=&#34;https://apurv.me/posts/kubernetes-routing-external-traffic-to-local-cluster/&#34;&gt;Kubernetes - Routing external traffic to local Kubernetes cluster&lt;/a&gt; to enable access to our internal cluster via public ip.&lt;/p&gt;
&lt;p&gt;We are using Cloudflare as our DNS Provider and implementing this solution using declarative GitOps principles with Flux.&lt;/p&gt;</description>
      
    </item>
    
  </channel>
</rss>
