EKS Addons should support upgrading version aligned with cluster version

[bryantbiggs]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

What is the outcome that you are trying to reach?

• When upgrading an EKS cluster with EKS addons (coredns, kube-proxy, aws-vpc-cni, etc.), I want to ensure that the version used is aligned with the cluster version. The API currently supports specifying either the default or latest for a given Kubernetes version

Describe the solution you would like

• The default behavior of the EKS addons provisioned/managed through EKS Blueprints should align the addon version with the given cluster version, allowing users to toggle between the default version or the latest version for the given cluster version

Describe alternatives you have considered

Additional context