Node Release Version is not updated or found

onabison commented 5 months ago

Expected Behaviour

Hello @mbeacom , I believe you helped me with this tool before...

When running the eksupgrade command: eksupgrade {cluste_name} 1.29 us-east-1 --force --latest-addons all available updates/versions should be found and updated. When I ran it just now, it did not detect the on-demand Release Version latest update as it seems to still have available updates.

Current Behaviour

eksupgrade staging-gcs-eks-cluster 1.29 us-east-1 --force --latest-addons
Upgrading cluster: staging-gcs-eks-cluster from version: 1.29 to 1.29...
Are you sure you want to proceed with the upgrade process against: staging-gcs-eks-cluster? [y/N]: y
The current version of the cluster was detected as: 1.29
Cluster: staging-gcs-eks-cluster already on version: 1.29! Skipping cluster upgrade!
Found the following Managed Nodegroups
        * on-demand
        * spot
Getting cluster managed nodegroup details...
Managed Node Group: on-demand - Version: 1.29 - Release Version: 1.29.0-20240415 - Cluster: staging-gcs-eks-cluster
Getting cluster managed nodegroup details...
Managed Node Group: spot - Version: 1.29 - Release Version: 1.29.0-20240415 - Cluster: staging-gcs-eks-cluster
Getting cluster autoscaling group details...
Autoscaling Group: eks-on-demand-6cc1fdfd-d8c1-f92c-e2b5-63706644407e - Cluster: staging-gcs-eks-cluster
Healthy Instances:
         * i-096aadfd7318e8f61
         * i-0b44cd39c6d258ea8
         * i-0da7ebaff0a4671a4
Getting cluster autoscaling group details...
Autoscaling Group: eks-spot-8cc1fdfb-f7c2-057a-031b-4ed7a29e8bbf - Cluster: staging-gcs-eks-cluster
The add-ons update has been initiated...
Fetching Cluster Addons...
Getting the list of current cluster addons for cluster: staging-gcs-eks-cluster...
No Cluster AutoScaler is Found
No outdated managed nodegroups found!
Found the following Self-managed Nodegroups:
EKS Cluster staging-gcs-eks-cluster UPDATED TO 1.29

Code snippet

I'm not sure there's any thing I can provide to reproduce this unless you build your own cluster and try to run the same with the same versions I currently have.

Possible Solution

No response

Steps to Reproduce

I'm not sure there's any thing I can provide to reproduce this unless you build your own cluster and try to run the same with the same versions I currently have.

I am not sure this is a bug and not all the fields that are required are relevant for me

Amazon EKS upgrade version

latest

Python runtime version

3.9

Packaging format used

PyPi

Debugging logs

No response

github-actions[bot] commented 4 months ago

This issue has not received any attention in 30 days. If you want to keep this issue open, please leave a comment below and auto-close will be canceled.

onabison commented 3 months ago

Hello I understand that the person who used to help me in this matter before has left AWS. May I ask that someone else pick this up?

aws-samples / eks-cluster-upgrade