Managed Kubernetes Price Comparison

Egress costs at those major clouds are ridiculous. Once you start having some traffic it can easily make 50% of all costs or more. That is not justifiable! Meanwhile hardware costs are going down. We need more k8s providers with more resonable pricing. Unfortunatelly both Digital Ocean and Oracle Cloud don't have proper network load balancer implementations which is a must for elastic regional clusters and to forward TCP in a way that client IP is preserved and be able to add nodes without downtimes or TCP resets. OVH cloud doesn't implement LoadBalancer service type at all. So the choice in 2020 is really just Google, Amazon, Azure with their rolls-royce pricing. The cost difference between them is neglible. And then there are confidential free credits for startups. So sad...

It doesn't seem to include Digital Ocean in the comparison.

Scaleway gives you a k8s cluster starting from 40 EUR per month

Only Azure doesn’t charge for the k8s control plane, that is the most surprising thing for me.

I'm not familiar with the space so my question might not be that relevant - where does OpenShift fit in all of this (I still struggle to differentiate it from Kubernetes) and is there any merit to IBM trying to sell it so hard?

Too bad AKS is just terrible.<p>Slow provisioning time, slow PVCs, slow LoadBalancer provisioning, slow node pool management, plus non-production ready node pool implementation.

Does anyone have experience with OVH&#x27;s managed k8s offering? I&#x27;ve had good experiences with them in the past on pricing&#x2F;quality.

As someone who manages a production cluster, I spend about 1% of my time worrying about the control plane. It’s trivial to get it running and keep it running now. It’s all the stuff you build on top of k8s that’s the hard part. I don’t see much value add to eks, personally.

<a href="https:&#x2F;&#x2F;aws.amazon.com&#x2F;en&#x2F;blogs&#x2F;aws&#x2F;amazon-eks-on-aws-fargate-now-generally-available&#x2F;" rel="nofollow">https:&#x2F;&#x2F;aws.amazon.com&#x2F;en&#x2F;blogs&#x2F;aws&#x2F;amazon-eks-on-aws-fargat...</a>

At the low end it’s worth considering Fargate distinct from EKS. You don’t need to provision a whole cluster (generally 3 machines minimum) and can just run as little as a single Pod.

Just curious - what&#x27;s wrong with buying a large instance (24 cores) and running it for &lt; 10,000 users? Kubernetes feels like an insane complexity that doesn&#x27;t need to be taken on and managed. You&#x27;re gonna spend more time managing Kubernetes than writing <i>actual</i> software. Also, it feels like if something goes wrong in prod with your cluster - you&#x27;re gonna need external help to get you back on the feet.<p>If you&#x27;re not going to build the next Facebook, why would you need so much complexity?

Will be nice to include GPUs in v2 once there is more stable support for the operators