Wrong "nodegroup" related output information on "upgrade cluster" command

[yogeek]

When the eksctl upgrade cluster command is launched with a modification on nodegroups in the YAML config file, the output wrongly indicates that all nodegroups have up-to-date configuration.

2021-10-21 13:21:42 [ℹ]  eksctl version 0.70.0
2021-10-21 13:21:42 [ℹ]  using region eu-central-1
2021-10-21 13:21:42 [!]  NOTE: cluster VPC (subnets, routing & NAT Gateway) configuration changes are not yet implemented
2021-10-21 13:21:42 [ℹ]  no cluster version update required
2021-10-21 13:21:43 [ℹ]  re-building cluster stack "eksctl-apigw-integration-cluster"
2021-10-21 13:21:43 [✔]  all resources in cluster stack "eksctl-apigw-integration-cluster" are up-to-date
2021-10-21 13:21:43 [ℹ]  checking security group configuration for all nodegroups
2021-10-21 13:21:43 [ℹ]  all nodegroups have up-to-date configuration

However, if I understood correctly the upgrade cluster does not handle nodegroups, does it ?

eksctl version : 0.70.0

[aclevername]

Thanks for opening the issue @yogeek . eksctl upgrade cluster is only for upgrading the clusters Kubernetes version or launch template, not any of the other fields. Nodegroups unfortunately are largely immutable after creation. You will need to delete & recreate the nodegroup to have any changes applied

[yogeek]

@aclevername yes I saw that, that's why I found the output I mentioned above misleading because it makes users think that the potential modifications they made about nodegroups have not been taken into account.
Why displaying information about nodegroups if the command does actually not manage nodegroups config...?

[aclevername]

@aclevername yes I saw that, that's why I found the output I mentioned above misleading because it makes users think that the potential modifications they made about nodegroups have not been taken into account. Why displaying information about nodegroups if the command does actually not manage nodegroups config...?

This message is referring to the nodegroup stack being up to date, as sometimes we have made changes to the stack that need to be migrated. Appreciate that it is slightly confusing. Opened #4393 to fix the message.