undefined | Better HN

0 pointswhatthecloud3mo ago0 comments

> If you go multi-cloud you need to learn a whole new set of systems.

Isn't the whole point of Kubernetes that you don't need to do this? Also, if you want to know for certain that you aren't "vendor locked", running on two clouds is a constant test of that fact. That is to say, have a stack that can deploy to Kubernetes then have two clusters in separate clouds.

0 comments

ExoticPearTree3mo ago

> Isn't the whole point of Kubernetes that you don't need to do this?

In theory.

In practice, all managed K8s offerings use different APIs to provision, monitor and so on. Then you have all kinds of ingresses that are offered by each cloud provider (setting up an ALB on AWS is quite different than setting up a GLB on GCP).

And you really don't want to run your own k8s cluster(s).

The only thing that is somewhat vanilla in all of this are how you run the pods of your app.

And K8s is not "the cloud", it is just an orchestration system for containers.

j / k navigate · click thread line to collapse