Chetan Patwal

`eksctl upgrade cluster` upgrades the control plane to a newer version, it does not attempt to create any new nodegroups defined in the ClusterConfig. To add new nodegroups, you'll have...

That is not supported. If you need that level of control, we recommend creating the VPC resources beforehand and supplying them to eksctl.

I have also encountered this and I think I know what the issue is. We'll work on a fix soon.

@ysicing, apologies for the delay. I'm occupied with other tasks and will need some time to review the new changes.

EKS 1.23 is not the default yet, so we'll have to wait a bit more before merging.

> EKS 1.23 is not the default yet, so we'll have to wait a bit more before merging. EKS 1.23 is now the default. This PR is good to merge.

This is blocked on AWS patching all existing EKS clusters to enable support for Windows IPAM on the control plane.

> @errordeveloper can you please help us here, this looks like a must have now. @rverma-nsl which eksctl operations are you trying to invoke and from what language?

There's `nodeGroup.securityGroups.attachIDs` that lets you specify existing security groups for your nodegroups. Does that work for your use case or do you not want the security group rules added by...

This is a useful feature, but we're wary of adding more instance selector options to eksctl to avoid bloating it with features only few are using. We're going to discuss...