Replies: 1 comment 1 reply
-
Currently the logic is choosing to use the default addon version for the given Kubernetes version. However this is a great callout and we should make some changes to address. Specifically, we can leave the current default behavior as is (use the default addon version for the given Kubernetes version), but allow users to specify a flag to use the latest addon version |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi,
I have been trying to use the provided AWS EKS Upgrade tool:
https://github.com/aws-samples/eks-cluster-upgrade
While using it I have noticed a few things that I'm not sure why they are occurring:
The add-on seems to be downgrading rather than upgrading, here's the output:
INFO:eksupgrade.src.k8s_client:coredns-79fffc5cf7-rtpnt Current Version = v1.8.7-eksbuild.3 Updating to = v1.8.7-eksbuild.2
I am curious to understand how does the tool determine what is the latest available version for the respective add-on. It seems there is a much newer version for each of the add-on's I have on my cluster, yet, it manages to downgrade. Even if it does find an upgrade version, it only makes a small (usually minor version) upgrade. here's an image that shows the current version the upgrade tool selected during the upgrade process and VS the latest version that is available for that particular add-on.
Beta Was this translation helpful? Give feedback.
All reactions