--- title: Part 2 on AWS: Rolling your own servers with K8s | daily.dev description: Covers how to design networking for a small bare metal Kubernetes cluster in a colocation facility, as an alternative to AWS. Discusses separating management,... canonical: https://daily.dev/posts/part-2-on-aws-rolling-your-own-servers-with-k8s-j3yxtjghd twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Part 2 on AWS: Rolling your own servers with K8s | daily.dev og:description: Covers how to design networking for a small bare metal Kubernetes cluster in a colocation facility, as an alternative to AWS. Discusses separating management,... og:url: https://daily.dev/posts/part-2-on-aws-rolling-your-own-servers-with-k8s-j3yxtjghd og:image: https://api.daily.dev/og/posts/j3YXTjghD.png og:image:alt: Part 2 on AWS: Rolling your own servers with K8s og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Part 2 on AWS: Rolling your own servers with K8s **[Teleport](https://daily.dev/sources/teleport)** · 7 min read · 0 upvotes · 0 comments ## Summary Covers how to design networking for a small bare metal Kubernetes cluster in a colocation facility, as an alternative to AWS. Discusses separating management, storage, and application LANs, the tradeoffs of host networking versus SDN, using MetalLB for floating public IPs, bandwidth capacity considerations, and remote server management via IPMI or iDRAC. Part of a three-part series comparing colocation to AWS. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### How do I get floating public IPs for Kubernetes on bare metal servers without AWS? Public IP space for a bare metal Kubernetes cluster can be managed using MetalLB, a load-balancer implementation for bare metal. You feed it the public IP block received from your colocation provider, and Kubernetes can then provision floating public IPs and load balancers for applications similarly to how AWS handles it. _daily.dev surfaces practical bare metal Kubernetes networking guides for teams moving off cloud providers._ ### What separate LANs should I set up for a bare metal Kubernetes colocation environment? A bare metal colocation setup should have at least three separate LANs: a management LAN for IPMI and switch access (ideally behind a VPN), a storage LAN for network-based storage volumes with a dedicated NIC per server, and an application LAN for workloads, similar to AWS VPCs. Each LAN needs its own non-overlapping address space. _Teams designing colocation networks can track infrastructure architecture patterns like this on daily.dev._ ## Similar posts on daily.dev - [An architectural decision: Containers on bare metal or on virtual machines](https://daily.dev/posts/an-architectural-decision-containers-on-bare-metal-or-on-virtual-machines-5dagnz43z) · CNCF · 2 upvotes · 0 comments - [Demystify the architecture of OpenShift hosted control planes](https://daily.dev/posts/demystify-the-architecture-of-openshift-hosted-control-planes-uqf6pa4wl) · Red Hat Developer · 1 upvotes · 0 comments - [When Kubernetes Meets Real Data Center Networking: Building a Routable, Resilient On-Prem Cluster with BGP and ECMP](https://daily.dev/posts/when-kubernetes-meets-real-data-center-networking-building-a-routable-resilient-on-prem-cluster-wi-6epvdu3rc) · Container Journal · 0 upvotes · 0 comments - [𝐇𝐲𝐛𝐫𝐢𝐝 𝐃𝐞𝐯𝐞𝐥𝐨𝐩𝐦𝐞𝐧𝐭 𝐖𝐨𝐫𝐤𝐟𝐥𝐨𝐰: 𝐅𝐫𝐨𝐦 𝐎𝐧-𝐏𝐫𝐞𝐦 𝐭𝐨 𝐀𝐖𝐒](https://daily.dev/posts/35wh6slad) · Medium · 1 upvotes · 0 comments - [Understanding Kubernetes Networking](https://daily.dev/posts/understanding-kubernetes-networking-oooxha7or) · cilium · 22 upvotes · 1 comments --- Tags: [#aws](https://daily.dev/tags/aws), [#kubernetes](https://daily.dev/tags/kubernetes), [#infrastructure](https://daily.dev/tags/infrastructure), [#networking](https://daily.dev/tags/networking) [View this post on daily.dev](https://daily.dev/posts/part-2-on-aws-rolling-your-own-servers-with-k8s-j3yxtjghd) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Part 2 on AWS: Rolling your own servers with K8s","url":"https://daily.dev/posts/part-2-on-aws-rolling-your-own-servers-with-k8s-j3yxtjghd","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/part-2-on-aws-rolling-your-own-servers-with-k8s-j3yxtjghd"},"datePublished":"2026-08-23T12:23:16.238Z","dateModified":"2026-08-23T12:56:56.481Z","description":"Covers how to design networking for a small bare metal Kubernetes cluster in a colocation facility, as an alternative to AWS. Discusses separating management,...","image":"https://media.daily.dev/image/upload/s--CxzD6vbw--/f_auto/v1722860399/public/Placeholder%2005","thumbnailUrl":"https://media.daily.dev/image/upload/s--CxzD6vbw--/f_auto/v1722860399/public/Placeholder%2005","isAccessibleForFree":true,"articleSection":"Teleport","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Teleport","logo":"https://media.daily.dev/image/upload/s--Dw-Bbw6O--/c_limit,w_256/f_auto,q_auto/v1787487494/logos/teleport?_a=BAMAMicg0","url":"https://daily.dev/sources/teleport"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/part-2-on-aws-rolling-your-own-servers-with-k8s-j3yxtjghd","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"aws,kubernetes,infrastructure,networking","timeRequired":"PT7M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Teleport","item":"https://daily.dev/sources/teleport"},{"@type":"ListItem","position":3,"name":"Part 2 on AWS: Rolling your own servers with K8s"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/part-2-on-aws-rolling-your-own-servers-with-k8s-j3yxtjghd#faq","mainEntity":[{"@type":"Question","name":"How do I get floating public IPs for Kubernetes on bare metal servers without AWS?","acceptedAnswer":{"@type":"Answer","text":"Public IP space for a bare metal Kubernetes cluster can be managed using MetalLB, a load-balancer implementation for bare metal. You feed it the public IP block received from your colocation provider, and Kubernetes can then provision floating public IPs and load balancers for applications similarly to how AWS handles it. daily.dev surfaces practical bare metal Kubernetes networking guides for teams moving off cloud providers."}},{"@type":"Question","name":"What separate LANs should I set up for a bare metal Kubernetes colocation environment?","acceptedAnswer":{"@type":"Answer","text":"A bare metal colocation setup should have at least three separate LANs: a management LAN for IPMI and switch access (ideally behind a VPN), a storage LAN for network-based storage volumes with a dedicated NIC per server, and an application LAN for workloads, similar to AWS VPCs. Each LAN needs its own non-overlapping address space. Teams designing colocation networks can track infrastructure architecture patterns like this on daily.dev."}}]} ```