<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Cilium on Support Tools</title><link>https://support.tools/tags/cilium/</link><description>Recent content in Cilium on Support Tools</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Sun, 25 Oct 2026 09:00:00 -0500</lastBuildDate><atom:link href="https://support.tools/tags/cilium/index.xml" rel="self" type="application/rss+xml"/><item><title>Cilium MTU Black Hole: How a Linux Bridge and KubeVirt VMs Silently Broke VXLAN and Kept Longhorn Degraded</title><link>https://support.tools/cilium-mtu-linux-bridge-kubevirt-vxlan-blackhole-longhorn-degraded/</link><pubDate>Sun, 25 Oct 2026 09:00:00 -0500</pubDate><guid>https://support.tools/cilium-mtu-linux-bridge-kubevirt-vxlan-blackhole-longhorn-degraded/</guid><description>&lt;p&gt;For about ten hours, roughly 45 Longhorn volumes on one of our production RKE2 clusters sat in a degraded state. Replicas flapped to &lt;code&gt;ERR&lt;/code&gt;, rebuilds started and failed, and the Longhorn event stream logged more than 1,400 replica errors, nearly 800 of them in a single hour on one node. Small API calls worked. DNS worked. Health checks were green. Only bulk traffic between certain pairs of nodes was disappearing, and which pairs changed over the course of the day.&lt;/p&gt;&#10;&lt;p&gt;The cause turned out to be three ordinary behaviors stacked on top of each other. A Linux bridge takes the MTU of its smallest port. KubeVirt VMs attach 1500-byte veths to that bridge. And Cilium, with no MTU configured, does not just read the device MTU at startup: it follows it while running. Pods keep the MTU they were created with. So every time a VM moved onto or off a node, that node&amp;rsquo;s tunnel MTU changed underneath pods that still believed the old value, and their large VXLAN packets went into a black hole with no error anywhere.&lt;/p&gt;&#10;&lt;p&gt;This post walks through the mechanism, a reproducible demonstration of the bridge behavior, the commands that prove it on a live cluster, the fix (pin the MTU, flatten the underlay), and the planned full-cluster outage it took to apply that fix safely.&lt;/p&gt;</description></item><item><title>Kubernetes Network Policies for Zero-Trust Architecture: Enterprise Implementation Guide</title><link>https://support.tools/kubernetes-network-policies-zero-trust-architecture-enterprise-guide/</link><pubDate>Thu, 03 Sep 2026 00:00:00 -0500</pubDate><guid>https://support.tools/kubernetes-network-policies-zero-trust-architecture-enterprise-guide/</guid><description>&lt;p&gt;Zero-trust network architecture represents a fundamental shift in cloud-native security strategy, requiring explicit authorization for every network connection rather than implicit trust based on network location. Kubernetes Network Policies provide the foundational building blocks for implementing zero-trust networking at the pod level. This comprehensive guide explores enterprise-grade network policy implementations using native Kubernetes Network Policies and advanced CNI-specific features from Calico and Cilium.&lt;/p&gt;</description></item><item><title>Cilium eBPF Networking Deep Dive: Advanced Kubernetes CNI Implementation</title><link>https://support.tools/cilium-ebpf-networking-deep-dive/</link><pubDate>Tue, 12 May 2026 00:00:00 -0500</pubDate><guid>https://support.tools/cilium-ebpf-networking-deep-dive/</guid><description>&lt;p&gt;Cilium represents a paradigm shift in Kubernetes networking by leveraging eBPF (extended Berkeley Packet Filter) technology to provide high-performance, secure, and observable networking capabilities. This comprehensive guide explores advanced Cilium implementation patterns, performance optimization techniques, and enterprise-grade configurations for production Kubernetes clusters.&lt;/p&gt;</description></item><item><title>Cilium BGP Control Plane for Kubernetes: Complete Enterprise Implementation Guide</title><link>https://support.tools/cilium-bgp-control-plane-kubernetes-enterprise-guide/</link><pubDate>Tue, 10 Feb 2026 09:00:00 -0500</pubDate><guid>https://support.tools/cilium-bgp-control-plane-kubernetes-enterprise-guide/</guid><description>&lt;p&gt;Bare-metal and on-premises Kubernetes clusters face a fundamental networking challenge that cloud providers solve transparently: making Services and Pods reachable from outside the cluster. In cloud environments, a LoadBalancer Service automatically provisions an external IP and programs the cloud provider&amp;rsquo;s network fabric. On bare metal, that integration does not exist. &lt;strong&gt;Border Gateway Protocol (BGP)&lt;/strong&gt; fills this gap by enabling Kubernetes nodes to advertise routes for Pod CIDRs, LoadBalancer IPs, and custom prefixes directly to the upstream network infrastructure.&lt;/p&gt;&#10;&lt;p&gt;Cilium&amp;rsquo;s &lt;strong&gt;BGP Control Plane&lt;/strong&gt; integrates this capability directly into the CNI layer. Built on the &lt;strong&gt;GoBGP&lt;/strong&gt; routing library, the BGP Control Plane runs a BGP speaker on each selected node, advertising routes to configured peers without requiring an external component like MetalLB. Combined with Cilium&amp;rsquo;s &lt;strong&gt;LB-IPAM&lt;/strong&gt; (LoadBalancer IP Address Management), this provides a complete, single-stack solution for bare-metal service exposure — from IP allocation through route advertisement to eBPF-accelerated packet forwarding.&lt;/p&gt;</description></item><item><title>Running K3s in an IPv6-Only Environment with Cilium</title><link>https://support.tools/k3s-ipv6-cilium/</link><pubDate>Sun, 01 Jun 2025 00:00:00 -0500</pubDate><guid>https://support.tools/k3s-ipv6-cilium/</guid><description>&lt;p&gt;Most guides for Kubernetes focus on IPv4 by default, but IPv6 is no longer a second-class citizen. In this post, I walk through configuring a &lt;strong&gt;K3s cluster using only IPv6&lt;/strong&gt;, with &lt;strong&gt;Cilium&lt;/strong&gt; as the CNI, and &lt;strong&gt;BGP&lt;/strong&gt; to announce addresses to my router. This setup runs entirely on a public IPv6 prefix—no dual-stack, no IPv4 fallback.&lt;/p&gt;</description></item><item><title>RKE2 the Hard Way: Part 8 – Installing Cilium CNI</title><link>https://support.tools/training/rke2-hard-way/08-installing-cilium-cni/</link><pubDate>Tue, 01 Apr 2025 00:00:00 +0000</pubDate><guid>https://support.tools/training/rke2-hard-way/08-installing-cilium-cni/</guid><description>&lt;h2 id="part-8--installing-cilium-cni"&gt;Part 8 – Installing Cilium CNI&lt;/h2&gt;&#10;&lt;p&gt;In this part of the &lt;strong&gt;&amp;ldquo;RKE2 the Hard Way&amp;rdquo;&lt;/strong&gt; training series, we will install and configure the &lt;strong&gt;Cilium CNI&lt;/strong&gt; (Container Network Interface). Cilium is a powerful, open-source CNI solution that provides advanced networking, security, and observability features for Kubernetes clusters.&lt;/p&gt;&#10;&lt;p&gt;At this point in our tutorial series, we have:&lt;/p&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;Set up all the core Kubernetes components (etcd, kube-apiserver, kube-controller-manager, kube-scheduler)&lt;/li&gt;&#10;&lt;li&gt;Configured kubelet and kube-proxy on our nodes&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;p&gt;However, our cluster network is not yet functional for pod-to-pod communication. The CNI plugin is essential for implementing the Kubernetes networking model, which requires that:&lt;/p&gt;</description></item><item><title>Cilium Troubleshooting Guide: Commands That Work in 2026</title><link>https://support.tools/post/cilium-troubleshooting-2025/</link><pubDate>Fri, 14 Mar 2025 14:00:00 -0500</pubDate><guid>https://support.tools/post/cilium-troubleshooting-2025/</guid><description>&lt;p&gt;Troubleshooting Cilium is mostly about running the right command in the right place. This guide is a working reference for current Cilium releases (1.16 through 1.20, with 1.20.3 the current stable at the time of this update): the cilium CLI on your workstation, &lt;code&gt;cilium-dbg&lt;/code&gt; inside the agent, and Hubble for flows. It builds on our earlier &lt;a href="https://support.tools/post/cilium-troubleshooting/"&gt;Cilium Troubleshooting Guide&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>Fixing Argo CD Out-of-Sync Due to Cilium Identity on RKE2</title><link>https://support.tools/cilium-identity-argo-out-of-sync-rke2/</link><pubDate>Tue, 15 Oct 2024 11:30:00 -0500</pubDate><guid>https://support.tools/cilium-identity-argo-out-of-sync-rke2/</guid><description>&lt;h2 id="fixing-argo-cd-out-of-sync-due-to-cilium-identity-on-rke2"&gt;Fixing Argo CD Out-of-Sync Due to Cilium Identity on RKE2&lt;/h2&gt;&#10;&lt;p&gt;If you&amp;rsquo;re running a Kubernetes cluster with RKE2 and Cilium as your networking solution, you might encounter a situation where Argo CD shows an out-of-sync status due to the presence of &lt;strong&gt;CiliumIdentity&lt;/strong&gt; resources. Although the actual application is in sync and functioning normally, this false out-of-sync status can be frustrating to see in your CI/CD workflows.&lt;/p&gt;</description></item><item><title>Cilium Troubleshooting Guide</title><link>https://support.tools/post/cilium-troubleshooting/</link><pubDate>Wed, 27 Mar 2024 10:00:00 -0500</pubDate><guid>https://support.tools/post/cilium-troubleshooting/</guid><description>&lt;p&gt;Troubleshooting Cilium in Kubernetes can be daunting. This guide provides steps and tools to help diagnose and resolve common issues. Utilize upstream guides and tools for in-depth analysis and health verification of your cluster&amp;rsquo;s Cilium deployment.&lt;/p&gt;</description></item><item><title>Navigating the Depths of Kubernetes Networking with Cilium: A Comprehensive Guide</title><link>https://support.tools/post/cilium-deepdive/</link><pubDate>Wed, 27 Mar 2024 10:00:00 -0500</pubDate><guid>https://support.tools/post/cilium-deepdive/</guid><description>&lt;p&gt;This guide embarks on a journey to unravel the complexities of Kubernetes networking and spotlights Cilium&amp;rsquo;s transformative role in the container orchestration landscape. Through an in-depth exploration, we&amp;rsquo;ll navigate the challenges and opportunities presented by integrating advanced Container Network Interface (CNI) solutions, focusing on Cilium&amp;rsquo;s capabilities and symbiotic relationship with eBPF technology.&lt;/p&gt;</description></item><item><title>Kubernetes Networking with Cilium: Understanding the Basics</title><link>https://support.tools/post/kubernetes-networking-cilium/</link><pubDate>Thu, 02 Feb 2023 23:51:00 -0600</pubDate><guid>https://support.tools/post/kubernetes-networking-cilium/</guid><description>&lt;p&gt;Kubernetes is an open-source platform for automating the deployment, scaling, and management of containerized applications. One of the key components of a Kubernetes deployment is its network infrastructure, and there are various solutions available to address this requirement. One such solution is Cilium, an open-source tool that provides advanced networking capabilities for Kubernetes.&lt;/p&gt;</description></item></channel></rss>