A lot of the EKS disadvantages, I've noticed, are from AWS attempting to make things complicated. On the GKE side it's really set and forget, just pick a release channel to subscribe to.
AWS makes you do things like manage node OS and addon versions, which is pretty ridiculous. I feel like it only exists to lock people in to ECS/Fargate and make people assume Kubernetes has to be complicated.
Comments
A lot of the EKS disadvantages, I've noticed, are from AWS attempting to make things complicated. On the GKE side it's really set and forget, just pick a release channel to subscribe to.
AWS makes you do things like manage node OS and addon versions, which is pretty ridiculous. I feel like it only exists to lock people in to ECS/Fargate and make people assume Kubernetes has to be complicated.
Author here,
Agreed and most people tend to go towards ECS is because they don’t have enough resources to manage EKS or Kuberenetes in general
Now Kuberenetes is really powerful in my opinion but sometimes it might be an overkill
You might even get away with EC2s but they bring extra overhead of management such as patches and os upgrades and autoscaling can be trivial
Is this the kind of thing EKS Auto Mode helps with? (For a price, of course)