<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Kubernetes on Landry Zetam - Tech Blog</title><link>https://blog.landryzetam.net/categories/kubernetes/</link><description>Recent content in Kubernetes on Landry Zetam - Tech Blog</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Tue, 16 Dec 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.landryzetam.net/categories/kubernetes/index.xml" rel="self" type="application/rss+xml"/><item><title>Enabling DNS-01 TLS for Internal Kubernetes Services</title><link>https://blog.landryzetam.net/posts/dns01-tls-kubernetes-internal-services/</link><pubDate>Tue, 16 Dec 2025 00:00:00 +0000</pubDate><guid>https://blog.landryzetam.net/posts/dns01-tls-kubernetes-internal-services/</guid><description>&lt;p>Ever visited a website and seen that little padlock icon in your browser? That&amp;rsquo;s TLS at work, encrypting the connection between you and the server. But what happens when you want that same security for services running on your home network that aren&amp;rsquo;t accessible from the internet? Today I solved this exact problem, and I want to walk you through not just &lt;em>how&lt;/em> I did it, but &lt;em>why&lt;/em> each piece matters.&lt;/p></description></item></channel></rss>