<?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 Ray Krueger</title><link>https://www.raykrueger.com/tags/kubernetes/</link><description>Recent content in Kubernetes on Ray Krueger</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 04 Aug 2026 00:00:00 -0500</lastBuildDate><atom:link href="https://www.raykrueger.com/tags/kubernetes/index.xml" rel="self" type="application/rss+xml"/><item><title>Cilium Ingress Dropped as Martian Source</title><link>https://www.raykrueger.com/posts/cilium-ingress-martian-source/</link><pubDate>Tue, 04 Aug 2026 00:00:00 -0500</pubDate><guid>https://www.raykrueger.com/posts/cilium-ingress-martian-source/</guid><description>&lt;h2 id="the-symptom"&gt;The symptom&lt;/h2&gt;&#10;&lt;p&gt;Single-node cluster at home. Cilium as the CNI, doing ingress and L2 load&#10;balancing. The goal was mundane: &lt;code&gt;https://api.llama.internal/&lt;/code&gt; should hit a&#10;&lt;code&gt;llamacpp&lt;/code&gt; pod through Cilium&amp;rsquo;s ingress.&lt;/p&gt;&#10;&lt;p&gt;It didn&amp;rsquo;t. From any machine on my LAN:&lt;/p&gt;&#10;&lt;pre tabindex="0"&gt;&lt;code&gt;$ curl -k --max-time 15 https://api.llama.internal/&#10;curl: (28) Connection timed out after 15004 milliseconds&#10;&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;The connection never even got to TLS. But here&amp;rsquo;s the part that sent me down a&#10;three-hour rabbit hole: &lt;strong&gt;from the node itself, it worked fine.&lt;/strong&gt;&lt;/p&gt;</description></item></channel></rss>