<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Coredns on NerdyNik</title><link>http://nerdynick.com/tags/coredns/</link><description>Recent content in Coredns on NerdyNik</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 28 Dec 2023 14:30:00 -0600</lastBuildDate><atom:link href="http://nerdynick.com/tags/coredns/index.xml" rel="self" type="application/rss+xml"/><item><title>Exposing Kubernetes Services with CoreDNS</title><link>http://nerdynick.com/posts/2023/12/exposing-kubernetes-services-with-coredns/</link><pubDate>Thu, 28 Dec 2023 14:30:00 -0600</pubDate><guid>http://nerdynick.com/posts/2023/12/exposing-kubernetes-services-with-coredns/</guid><description>&lt;blockquote class="alert alert-note"&gt;
 &lt;p class="alert-heading"&gt;
 ℹ️
 
 Note
 
 &lt;/p&gt;
 &lt;p&gt;Originall this article only made mention of the &lt;a href="https://github.com/ori-edge/k8s_gateway" target="_blank" rel="noopener"&gt;ori-edge/k8s_gateway&lt;/a&gt; project.
This project is now no longer maintained and development as switched over to &lt;a href="https://github.com/k8s-gateway/k8s_gateway" target="_blank" rel="noopener"&gt;k8s-gateway/k8s_gateway&lt;/a&gt;.&lt;/p&gt;
 &lt;/blockquote&gt;
&lt;p&gt;In my efforts to run a self-hosted Kubernetes cluster(s) in my lab.
I needed a way to easily expose services outside of the cluster for easy use by me and the family/friends.
In my research, I stumbled upon the Kubernetes Sig &lt;a href="https://github.com/kubernetes-sigs/external-dns" target="_blank" rel="noopener"&gt;ExternalDNS&lt;/a&gt;.
Its goal is to leverage K8 Service Annotates to provide the desired external DNS entry values and the respective configs to go along with it.
However, in my attempt to make this work in a self-hosted environment with minimal deployment in a small footprint on small hardware (RPis mostly), I came across many challenges.
Many of the integrations that ExternalDNS supports are focused on Cloud Provider DNS services rather than self-hosted one.
Of the self-hosted DNS options, many have large footprints in their deployments.
Such as the need for Databases or other services.
This left me looking at my favorite DNS service, CoreDNS.
However, in an attempt to get the CoreDNS ExternalDNS integration to work.
I found out that it requires an &lt;a href="https://etcd.io/" target="_blank" rel="noopener"&gt;etcd&lt;/a&gt; service to be available.
As well as that the plugins the integration relies on at both the ExternalDNS and CoreDNS sides appear to not be maintained much anymore.
Yet alone, the etcd approach is seen as a deprecated one in its own right.&lt;/p&gt;</description></item></channel></rss>