Mike Stefaniak

Closing as this service controller has graduated to GA. Separate issues can be opened to discuss specific follow on topics on the controller.

Closing as this service controller has graduated to GA. Separate issues can be opened to discuss specific follow on topics on the controller.

Closing as this service controller has graduated to GA. Separate issues can be opened to discuss specific follow on topics on the controller.

Closing as this service controller has graduated to GA. Separate issues can be opened to discuss specific follow on topics on the controller.

Closing as this service controller has graduated to GA. Separate issues can be opened to discuss specific follow on topics on the controller.

This is a known limitation, and the workaround you are doing is correct. It's impossible for EKS to know if a custom AMI is going to be used in a...

EKS does not maintain Ubuntu AMIs. This would be a feature request you need to make to Canonical.

You could use ACK to manage the addon in a Kubernetes native way https://aws-controllers-k8s.github.io/community/reference/eks/v1alpha1/addon/

See this issue https://github.com/awslabs/amazon-eks-ami/issues/626, gp3 is the default for 1.27+ with the EKS optimized AMI.

Ok it turns that PR that enabled gp3 for 1.27 was reverted, because some AWS Local Zones only support gp2. Gathering more info on this.