<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Bare-Metal on Ashish Jaiswal</title>
    <link>https://ashish1099.me/tags/bare-metal/</link>
    <description>Recent content in Bare-Metal on Ashish Jaiswal</description>
    <generator>Hugo -- 0.147.0</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 19 Mar 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://ashish1099.me/tags/bare-metal/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Cilium on Bare Metal: How UFW Silently Breaks CoreDNS and kube-apiserver Connectivity</title>
      <link>https://ashish1099.me/posts/cilium-bare-metal-ufw-coredns-kube-apiserver/</link>
      <pubDate>Thu, 19 Mar 2026 00:00:00 +0000</pubDate>
      <guid>https://ashish1099.me/posts/cilium-bare-metal-ufw-coredns-kube-apiserver/</guid>
      <description>&lt;h2 id=&#34;the-symptom&#34;&gt;The Symptom&lt;/h2&gt;
&lt;p&gt;After standing up a Kubernetes cluster on a bare-metal node with Cilium as the CNI, CoreDNS pods were
running but completely unable to reach the kube-apiserver service IP (&lt;code&gt;10.96.0.1&lt;/code&gt;). DNS resolution inside
the cluster was broken, and any pod trying to talk to the API server via the service IP timed out.&lt;/p&gt;
&lt;p&gt;The apiserver itself was healthy — direct connections to the node&amp;rsquo;s IP worked fine. The problem was
specifically with the virtual service IP routed through Cilium&amp;rsquo;s BPF dataplane.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
