Right now users have to find the right addon version to use with the cluster when using the Addon component. Otherwise it'll use the default version and never update. This can be problematic when updating the cluster and the addons are no longer compatible with the new cluster version.
The component should look up the correct version and set it by default. This can differentiate between the latest and EKS recommended version.
const addonVersion = aws.eks.getAddonVersionOutput(
{
addonName: "vpc-cni",
kubernetesVersion: clusterVersion,
mostRecent: true, // set to false to use the recommended version
},
).version;
Right now users have to find the right addon version to use with the cluster when using the
Addon
component. Otherwise it'll use the default version and never update. This can be problematic when updating the cluster and the addons are no longer compatible with the new cluster version.The component should look up the correct version and set it by default. This can differentiate between the latest and EKS recommended version.