<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Kube-Proxy on marktaguiad.dev</title>
    <link>https://marktaguiad.dev/tags/kube-proxy/</link>
    <description>Recent content in Kube-Proxy on marktaguiad.dev</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <managingEditor>marktaguiad@marktaguiad.dev (Mark Taguiad)</managingEditor>
    <webMaster>marktaguiad@marktaguiad.dev (Mark Taguiad)</webMaster>
    <copyright>marktaguiad.dev</copyright>
    <lastBuildDate>Fri, 24 Apr 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://marktaguiad.dev/tags/kube-proxy/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Cilium ClusterMesh: Connecting Kubernetes Clusters</title>
      <link>https://marktaguiad.dev/post/k8s-cilium-clustermesh/</link>
      <pubDate>Fri, 24 Apr 2026 00:00:00 +0000</pubDate><author>marktaguiad@marktaguiad.dev (Mark Taguiad)</author>
      <guid>https://marktaguiad.dev/post/k8s-cilium-clustermesh/</guid>
      <description>&lt;p&gt;Cilium is a Kubernetes CNI built on eBPF, replacing the traditional iptables-heavy networking model with kernel-level packet processing. Instead of relying on large iptables chains for routing, filtering, and service load balancing, Cilium injects eBPF programs directly into the Linux kernel datapath for lower latency and better scalability.&lt;/p&gt;&#xA;&lt;p&gt;This would require a whole book in explaining eBPF, so we will not dwell in that. Let&amp;rsquo;s focus first on connecting two Kubernetes Cluster.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
