| ▲ | esseph 3 days ago | |
> Moving from google cloud to AWS was a complete writeoff almost - just build it again. Yep. Kubernetes is not just kubernetes when moving between clouds, it becomes a very opinionated product (for better or worse) with lots of vendor addons. Could someone that is familiar with one pick up on the other? Sure! But there are gotchas. And then kubernetes on prem adds the hardware lifecycle piece, and potential data locality issues, etc. | ||
| ▲ | physicles 3 days ago | parent | next [-] | |
There are differences across vendors, but there’s a way to build with k8s where the benefit far outweighs the cost. We run a bunch of services in two very different cloud vendors (one of which used to be DIYed with kubeadm), and also on dev machines with k3s. Takes a while to figure this out and to draw the kustomize boundaries in the right place, but once you do, it’s actually really nice. Two things work in our favor: - we’ve been at this for around 8 years, so we didn’t have to deal with all the gotchas at once - we aggressively avoid tech that isn’t universal (so S3 is OK, but SQS or DynamoDB is not; use haproxy instead of ingress controllers; etc) | ||
| ▲ | philipallstar 2 days ago | parent | prev [-] | |
> Kubernetes is not just kubernetes when moving between clouds, it becomes a very opinionated product (for better or worse) with lots of vendor addons. I think this is gradually getting better. Networking with Gateways is better than with Ingress in this sense. Things like autoscaling groups need to get better, as they are (or were a couple of years ago) very bespoke. | ||