3 ms·

My biggest issue with Kubernetes is huge costs of running it. It's 3 servers with 4 GB RAM. It's almost $100/month just for Kubernetes alone. And you need one l

My biggest issue with Kubernetes is huge costs of running it. It's 3 servers with 4 GB RAM. It's almost $100/month just for Kubernetes alone. And you need one load balancer for control nodes which is another $25 for my hoster. And you need second load balancer for production workloads which is another $25. So you have to pay $150/month for the privilege of using Kubernetes. And they double your costs for your application, because you want it to be high-available, why bother with Kubernetes otherwise. So something that could be run with $5 droplet, suddenly requires $200. They you want to install grafana, ELK, service mesh and whatnot.

tux3 4y ago
k3s will run on a $5 droplet happily. If you want k8s for the yaml and not for the heavy-duty hyperscale redundancy, k3s works great
- vbezhenar 4y ago
  It's hard to stop when HA is one config line (and few additional dozens of bucks) away.
yjftsjthsd-h 4y ago
You don't actually need all that. If the competition is a single $5 machine with no redundancy, you can just run a single node cluster.
jeroenhd 4y ago
Three machines with 4GB of RAM for $100? I don't know where you rent your servers but that's ridiculous. You can easily get that kind of compute for a third or lower. You won't get a private LAN (so you'll need some firewall rules on the hoster side) and you'll have to do some setup to get everything served up on the right public IP address(es), but you don't need a dedicated load balancer product. Unless you expect your virtual servers to go down randomly, I suppose. I've set up k0s on Oracle's free service to mess with. It doesn't need nearly as much as 12GiB of RAM. Give it 500MiB per machine to be happy and it _should_ run fine with 10.5GiB to spare unless you're adding tons of overlays and additional services on top of your applications. As far as I can tell, the biggest cost with Kubernetes is maintaining the system and keeping up to date with the advancements and deprecations in the Kubernetes field. You can't just upgrade the Kubernetes version and expect everything to work, and every new concept that replaces anything old comes with Kubernetes layers of complexity. I honestly don't know what so many companies are using all those resources Kubernetes provides for. I have a feeling people are so caught up in the "modern server management" world that they've forgotten how powerful and reliable a $25 VPS is these days.
- mitjam 4y ago
  The simplest and cheapest self hosted K8s I found is kube-Hetzner [1]. It puts k3s on MicroOS on Hetzner Cloud; for a three node Cluster I pay around 50 EUR per month (3shared AMD Cores, 4GB RAM per Node, 200 GB Storage, 1 TB Backup, small loadbalancer). A single server with the same spec and the same storage and backup and a floating IP would go for about 25 EUR/month. For me, k8s is worth the difference. [1] https://registry.terraform.io/modules/kube-hetzner/kube-hetzner/hcloud/latest https://registry.terraform.io/modules/kube-hetzner/kube-hetz...

tux3 4y ago

k3s will run on a $5 droplet happily. If you want k8s for the yaml and not for the heavy-duty hyperscale redundancy, k3s works great

vbezhenar 4y ago
It's hard to stop when HA is one config line (and few additional dozens of bucks) away.

yjftsjthsd-h 4y ago

You don't actually need all that. If the competition is a single $5 machine with no redundancy, you can just run a single node cluster.

jeroenhd 4y ago

Three machines with 4GB of RAM for $100? I don't know where you rent your servers but that's ridiculous. You can easily get that kind of compute for a third or lower. You won't get a private LAN (so you'll need some firewall rules on the hoster side) and you'll have to do some setup to get everything served up on the right public IP address(es), but you don't need a dedicated load balancer product. Unless you expect your virtual servers to go down randomly, I suppose. I've set up k0s on Oracle's free service to mess with. It doesn't need nearly as much as 12GiB of RAM. Give it 500MiB per machine to be happy and it _should_ run fine with 10.5GiB to spare unless you're adding tons of overlays and additional services on top of your applications. As far as I can tell, the biggest cost with Kubernetes is maintaining the system and keeping up to date with the advancements and deprecations in the Kubernetes field. You can't just upgrade the Kubernetes version and expect everything to work, and every new concept that replaces anything old comes with Kubernetes layers of complexity. I honestly don't know what so many companies are using all those resources Kubernetes provides for. I have a feeling people are so caught up in the "modern server management" world that they've forgotten how powerful and reliable a $25 VPS is these days.

mitjam 4y ago
The simplest and cheapest self hosted K8s I found is kube-Hetzner [1]. It puts k3s on MicroOS on Hetzner Cloud; for a three node Cluster I pay around 50 EUR per month (3shared AMD Cores, 4GB RAM per Node, 200 GB Storage, 1 TB Backup, small loadbalancer). A single server with the same spec and the same storage and backup and a floating IP would go for about 25 EUR/month. For me, k8s is worth the difference. [1] https://registry.terraform.io/modules/kube-hetzner/kube-hetzner/hcloud/latest https://registry.terraform.io/modules/kube-hetzner/kube-hetz...