--- title: Part 3 on AWS: Rolling your own servers with K8s | daily.dev description: Comparing Kubernetes to traditional virtualization for teams considering leaving AWS to run bare metal servers. Covers gaps in networking, storage, tenant... canonical: https://daily.dev/posts/part-3-on-aws-rolling-your-own-servers-with-k8s-xjp1cpio8 twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Part 3 on AWS: Rolling your own servers with K8s | daily.dev og:description: Comparing Kubernetes to traditional virtualization for teams considering leaving AWS to run bare metal servers. Covers gaps in networking, storage, tenant... og:url: https://daily.dev/posts/part-3-on-aws-rolling-your-own-servers-with-k8s-xjp1cpio8 og:image: https://api.daily.dev/og/posts/xJP1CpIO8.png og:image:alt: Part 3 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 3 on AWS: Rolling your own servers with K8s **[Teleport](https://daily.dev/sources/teleport)** · 14 min read · 0 upvotes · 0 comments ## Summary Comparing Kubernetes to traditional virtualization for teams considering leaving AWS to run bare metal servers. Covers gaps in networking, storage, tenant isolation and legacy app support when running K8s on bare metal, strategies for managing stateful applications and databases, and how Kubernetes changes configuration management, CI/CD tooling, and application portability. Concludes Kubernetes is a strong alternative to virtualization unless secure multi-tenant isolation is required, and closes with a pitch for the author's own Gravity and Teleport open source projects. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### Should I run databases directly inside Kubernetes or keep them external? Distributed databases like Cassandra, HDFS, or MongoDB predate Kubernetes and already have built-in clustering, replication, and load-balancing, so they can run outside the cluster on dedicated nodes and be exposed to in-cluster applications via Kubernetes external services. Alternatively, network-attached storage with persistent volumes, stateful sets, and database-aware operators allows running stateful workloads inside Kubernetes when needed. _Teams weighing database placement in kubernetes clusters can track architecture tradeoffs like this on daily.dev._ ### Why is Kubernetes considered problematic for stateful applications like databases? Kubernetes was originally designed to favor stateless network services that only consume CPU, network, and memory, since it needs to move applications across servers to maximize infrastructure utilization. A database chained to local storage on a specific host cannot be freely relocated, which conflicts with that scheduling model and creates operational challenges for stateful workloads. _daily.dev helps engineers dig into recurring kubernetes state-management tradeoffs like this one._ ### What are the main things missing when running Kubernetes on bare metal instead of a cloud provider? Bare metal Kubernetes typically lacks mature software-defined networking comparable to cloud VPCs, robust virtualized storage with snapshotting and live migration, strong tenant isolation for untrusted third-party code, and easy support for legacy applications reliant on local storage. Native Kubernetes networking suffices for simple setups, but advanced SDN, enterprise storage, and hypervisor-grade isolation remain less mature than in public clouds. _Engineers planning a move off AWS to bare metal can weigh gaps like these using 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 - [Medium](https://daily.dev/posts/medium-htpmregrn) · Medium · 0 upvotes · 0 comments - [The Bare Metal Myth: Why VMs Now Win for Containers](https://daily.dev/posts/the-bare-metal-myth-why-vms-now-win-for-containers-bqrhosu0v) · The New Stack · 3 upvotes · 0 comments - [Hybrid Cloud at Enterprise Scale: Private Kubernetes for Portability and Control](https://daily.dev/posts/hybrid-cloud-at-enterprise-scale-private-kubernetes-for-portability-and-control-j1oyxy6b1) · Cloud Native Now · 0 upvotes · 0 comments - [Building a Kubernetes Cluster as a Service platform on BareMetal using KubeVirt and ClusterAPI](https://daily.dev/posts/building-a-kubernetes-cluster-as-a-service-platform-on-baremetal-using-kubevirt-and-clusterapi-w1rv27p3m) · ITNEXT · 0 upvotes · 0 comments --- Tags: [#kubernetes](https://daily.dev/tags/kubernetes), [#infrastructure](https://daily.dev/tags/infrastructure), [#cicd](https://daily.dev/tags/cicd) [View this post on daily.dev](https://daily.dev/posts/part-3-on-aws-rolling-your-own-servers-with-k8s-xjp1cpio8) ```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 3 on AWS: Rolling your own servers with K8s","url":"https://daily.dev/posts/part-3-on-aws-rolling-your-own-servers-with-k8s-xjp1cpio8","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/part-3-on-aws-rolling-your-own-servers-with-k8s-xjp1cpio8"},"datePublished":"2026-08-23T12:23:14.645Z","dateModified":"2026-08-23T12:53:31.518Z","description":"Comparing Kubernetes to traditional virtualization for teams considering leaving AWS to run bare metal servers. Covers gaps in networking, storage, tenant...","image":"https://media.daily.dev/image/upload/s--HRgLpUt6--/f_auto/v1722860399/public/Placeholder%2003","thumbnailUrl":"https://media.daily.dev/image/upload/s--HRgLpUt6--/f_auto/v1722860399/public/Placeholder%2003","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-3-on-aws-rolling-your-own-servers-with-k8s-xjp1cpio8","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"kubernetes,infrastructure,cicd","timeRequired":"PT14M"} {"@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 3 on AWS: Rolling your own servers with K8s"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/part-3-on-aws-rolling-your-own-servers-with-k8s-xjp1cpio8#faq","mainEntity":[{"@type":"Question","name":"Should I run databases directly inside Kubernetes or keep them external?","acceptedAnswer":{"@type":"Answer","text":"Distributed databases like Cassandra, HDFS, or MongoDB predate Kubernetes and already have built-in clustering, replication, and load-balancing, so they can run outside the cluster on dedicated nodes and be exposed to in-cluster applications via Kubernetes external services. Alternatively, network-attached storage with persistent volumes, stateful sets, and database-aware operators allows running stateful workloads inside Kubernetes when needed. Teams weighing database placement in kubernetes clusters can track architecture tradeoffs like this on daily.dev."}},{"@type":"Question","name":"Why is Kubernetes considered problematic for stateful applications like databases?","acceptedAnswer":{"@type":"Answer","text":"Kubernetes was originally designed to favor stateless network services that only consume CPU, network, and memory, since it needs to move applications across servers to maximize infrastructure utilization. A database chained to local storage on a specific host cannot be freely relocated, which conflicts with that scheduling model and creates operational challenges for stateful workloads. daily.dev helps engineers dig into recurring kubernetes state-management tradeoffs like this one."}},{"@type":"Question","name":"What are the main things missing when running Kubernetes on bare metal instead of a cloud provider?","acceptedAnswer":{"@type":"Answer","text":"Bare metal Kubernetes typically lacks mature software-defined networking comparable to cloud VPCs, robust virtualized storage with snapshotting and live migration, strong tenant isolation for untrusted third-party code, and easy support for legacy applications reliant on local storage. Native Kubernetes networking suffices for simple setups, but advanced SDN, enterprise storage, and hypervisor-grade isolation remain less mature than in public clouds. Engineers planning a move off AWS to bare metal can weigh gaps like these using daily.dev."}}]} ```