What is it giving you over an ec2 auto scaling group or ECS/Fargate?
Both can scale as much as you like, your config can live as cdk/cloudformation/terraform code?
Also something like karpenter.sh is much nicer than ec2 autoscaling group.
Yes, you can build an amazon machine image for ec2, update your cluster with the new image, without scaling from zero.
> As others have already pointed out, it is also important for us to remain independent from Google Cloud / AWS.
This seems like a good reason to use k8s, although as the original article touches on, it seems like switch cloud vendor rarely ever happens.
A lot of data tools are starting to target Kubernetes directly as a runtime so using them with GKE/EKS is a bit simpler as it’s officially supported, allows to run locally and on the cloud with no vendor lock in.
ECS in a scaling group works well if your app is stateless but as soon as you scale workers dynamically, do service discovery, orchestration, you end up building some of the features Kubernetes provides.