[cs02rm0]

With k8s - you switched to it, now what? You have to buy server hardware, rent or build a room, run wires for electricity and broadband, build cooling, physical security, etc etc etc.

I'm not sure that's the choice. You can run kubernetes in the cloud, can't you? e.g. EKS on Amazon.

[paulftw]

So you also agree that there's no standoff between AWS and K8s, unlike an article titled "'AWS vs. K8s' Is the New 'Win vs Linux'" would suggest?

It also talks about building a personal data center quite a few times (at least that's how I read it).

K8s is likely to replace EC2, ECS, and all other unusable amazon bloat to become the default AWS API. But it's not going to damage AWS, it's going to enhance it and become part of it.

[marcinzm]

AWS is an expensive cloud provider. If you commoditize it then then Amazon will either have to charge less (= less revenue/profits) or user will switch to cheaper cloud providers (= less aws revenue/profits). That is the point the article is making.

[xearl]

but even in this reply you describe the standoff very well yourself: after k8s replaces all amazon bloat to become the default AWS api, k8s has effectively commoditised AWS. i think that's precisely the point OP is also making.

[martingxx]

Running k8s in AWS (and gcp, and on-prem) is exactly what we do and we're really happy with it and have avoided lock-in. We recently moved a bunch of k8s-in-AWS hosted stuff to gcp and it was seamless.