Deploying Kubernetes Clusters on OpenStack: An Alternative to AWS EKS

https://hackernoon.imgix.net/images/jyoERDPm40MTLT2y9RyVLWqo7kO2-39935ul.png

Self-managed Kubernetes makes sense when you want to save some of your engineering budget. With OpenStack, you still get API-driven provisioning, private networking, and standard Terraform tooling without paying for a managed control plane.

A three-node k3s cluster on cloud comes at about $346/month. A comparable EKS setup in us-east-1 costs around $914/month before adding load balancers, NAT gateways, storage, and egress.

In this post, I’ll explain how we built this setup on an OpenStack provider, why VMs make more sense than bare metal for this architecture, and where the cost and operational trade-offs come from.

Bare metal servers still win on raw price per GB of RAM. You pay for them in time. It can take hours or even days to get one up and running, and a dead disk has to be physically swapped.

3HCloud is somewhere in between. You don’t have to use a shared pool, as...

Copyright of this story solely belongs to hackernoon.com. To see the full text click HERE