-
Notifications
You must be signed in to change notification settings - Fork 267
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
eksctl anywhere upgrade cluster doesn't use the extra hardware from hardware.csv #7818
Comments
From the initial look what I understand is this was a rolling and scaling upgrade request. This means that 2 extra hardwares were expected for the upgrade - 1 for the scale up, 1 spare for the rolling upgrade of 1.26 -> 1.27. My guess is that the extra hardware you added to the csv was used for the new CP node and eks anywhere didn't have enough for the rolling upgrade. |
@mitalipaygude I just try to use 1 more machine (1 existing host + 2 idle hosts), same issue shows:
At the same time, according to https://anywhere.eks.amazonaws.com/docs/clustermgmt/cluster-upgrades/baremetal-upgrades/:
So 1 spare machine is good enough. |
What happened:
I created an EKS anywhere cluster with 1 CP node, kubernetes 1.26
Then I try to upgrade it to 1.27, with 2 new CP nodes plus the existing CP node in the new hardware file.
cluster config file change is:
hardware change is:
The command I use:
eksctl anywhere upgrade cluster -f eksa-mgmt02-md-cluster-sc.yaml --hardware-csv hardware-mgmt02-cp3.csv --no-timeouts -v 9
I see upgrade stuck with following errors:
What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:
The text was updated successfully, but these errors were encountered: