At first glance this feels very much like GKE Autopilot and/or AKS Automatic. So now all three cloud providers have a more-fully-managed managed Kubernetes.
Part of the reason why they are including the managed add-ons is that they likely are going to be blocking your ability to escape your container with privileged DaemonSets to run things like those yourself in this model. GKE did something similar but eventually had to build a program for their security and observability partners to have their agent DaemonSets allow-listed through their block so that their tools could run on Autopilot - https://cloud.google.com/kubernetes-engine/docs/resources/au.... We'll see if AWS ends up doing a similar thing there too.
I have been in a platform team who tends towards analysis-paralysis and wanting to not use any of the managed EKS stuff as well as a security/compliance team getting more active/aggressive around our K8s. So it might be nice actually to just have fewer choices "e.g. sorry - we have to use the AWS CNI / Load Balancer Controller because EKS Auto" as well as throw more of the compliance stuff over the fence at AWS (assuming they get all the usual compliance certs on it).
But I am sure there'll be some sort of limitation(s) that keeps us from using it for the foreseeable future - so I am not getting my hopes up in the short term...
Part of the reason why they are including the managed add-ons is that they likely are going to be blocking your ability to escape your container with privileged DaemonSets to run things like those yourself in this model. GKE did something similar but eventually had to build a program for their security and observability partners to have their agent DaemonSets allow-listed through their block so that their tools could run on Autopilot - https://cloud.google.com/kubernetes-engine/docs/resources/au.... We'll see if AWS ends up doing a similar thing there too.
I have been in a platform team who tends towards analysis-paralysis and wanting to not use any of the managed EKS stuff as well as a security/compliance team getting more active/aggressive around our K8s. So it might be nice actually to just have fewer choices "e.g. sorry - we have to use the AWS CNI / Load Balancer Controller because EKS Auto" as well as throw more of the compliance stuff over the fence at AWS (assuming they get all the usual compliance certs on it).
But I am sure there'll be some sort of limitation(s) that keeps us from using it for the foreseeable future - so I am not getting my hopes up in the short term...