<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Bare-Metal on Support Tools</title><link>https://support.tools/tags/bare-metal/</link><description>Recent content in Bare-Metal on Support Tools</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Tue, 22 Sep 2026 00:00:00 -0500</lastBuildDate><atom:link href="https://support.tools/tags/bare-metal/index.xml" rel="self" type="application/rss+xml"/><item><title>MetalLB BGP Configuration for Bare Metal Kubernetes: Enterprise Load Balancer Guide</title><link>https://support.tools/metallb-bgp-configuration-bare-metal-kubernetes-guide/</link><pubDate>Tue, 22 Sep 2026 00:00:00 -0500</pubDate><guid>https://support.tools/metallb-bgp-configuration-bare-metal-kubernetes-guide/</guid><description>&lt;p&gt;MetalLB brings cloud-provider LoadBalancer functionality to bare metal Kubernetes clusters, enabling the use of LoadBalancer-type Services without relying on external cloud infrastructure. Operating in either Layer 2 (ARP/NDP) or BGP mode, MetalLB provides enterprise-grade load balancing capabilities essential for on-premises and edge Kubernetes deployments.&lt;/p&gt;&#10;&lt;p&gt;This comprehensive guide focuses on BGP mode configuration, which provides superior scalability, true load balancing across multiple nodes, and integration with existing network infrastructure. We&amp;rsquo;ll cover installation, BGP peering configuration, advanced routing scenarios, high availability patterns, and production-tested practices for enterprise bare metal Kubernetes environments.&lt;/p&gt;</description></item><item><title>Enterprise MetalLB Implementation: Advanced Bare-Metal Load Balancing for Production Kubernetes</title><link>https://support.tools/enterprise-metallb-bare-metal-load-balancing-kubernetes/</link><pubDate>Wed, 01 Jul 2026 00:00:00 -0500</pubDate><guid>https://support.tools/enterprise-metallb-bare-metal-load-balancing-kubernetes/</guid><description>&lt;p&gt;Bare-metal Kubernetes clusters lack cloud provider load balancer integration, creating challenges for exposing services externally. MetalLB bridges this gap by providing native load balancer capabilities for on-premises deployments. This comprehensive guide demonstrates enterprise-grade MetalLB implementation with advanced BGP routing, Layer 2 failover, multi-protocol support, and production monitoring strategies for mission-critical infrastructure.&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>RKE2 the Hard Way: Part 1 – Introduction and Prerequisites for Building a Kubernetes Cluster</title><link>https://support.tools/training/rke2-hard-way/01-introduction-prerequisites/</link><pubDate>Tue, 01 Apr 2025 00:00:00 +0000</pubDate><guid>https://support.tools/training/rke2-hard-way/01-introduction-prerequisites/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;&#10;&lt;p&gt;Welcome to the &lt;strong&gt;&amp;ldquo;RKE2 the Hard Way&amp;rdquo;&lt;/strong&gt; training series! In this series, we’ll embark on a journey to build a Kubernetes cluster from scratch—mimicking the robust features of Rancher Kubernetes Engine 2 (RKE2)—without relying on any distribution-specific tools or installers.&lt;/p&gt;&#10;&lt;p&gt;It&amp;rsquo;s called the &lt;em&gt;&amp;ldquo;hard way&amp;rdquo;&lt;/em&gt; because we&amp;rsquo;ll manually configure and set up each component of the Kubernetes cluster. This approach is designed to provide a deep understanding of how Kubernetes works under the hood and to highlight the automation and simplification RKE2 provides.&lt;/p&gt;</description></item><item><title>Exposing Services in Kubernetes Using External IPs</title><link>https://support.tools/post/kubernetes-external-ip/</link><pubDate>Fri, 20 Dec 2019 08:00:00 -0500</pubDate><guid>https://support.tools/post/kubernetes-external-ip/</guid><description>&lt;p&gt;Exposing services in Kubernetes effectively and securely is a common challenge, especially when working with bare metal deployments. NodePort might be the go-to solution for many, but it comes with its own set of limitations, such as the need to expose high-numbered ports and adjust firewall rules accordingly. Fortunately, Kubernetes offers another way to expose services using their original port numbers through the External IP service type. This post dives into how to leverage External IPs for service exposure in a Kubernetes cluster.&lt;/p&gt;</description></item></channel></rss>