eksctl
eksctl copied to clipboard
[Bug] EKSCTL doesn't recognise new nodegroup after failing to create one with bad configuration
What were you trying to accomplish?
Create an IPv6 cluster
What happened?
In my config.yaml, I had added a simple nodeGroup (which is unmanaged). Cluster creation stops with Eksctl saying
022-08-16 19:52:08 [✖] unmanaged nodegroups are not supported with IPv6 clusters
Following this, I tried to fix the config by changing to managedNodeGroups and running upgrade, however on upgrade eksctl claimed everything is fine
2022-08-16 19:55:27 [✔] all resources in cluster stack "eksctl-ae-eks-experimental-cluster" are up-to-date
How to reproduce it?
Setup config.yaml with ipv6 cluster and nodeGroups. After failure, update nodeGroups to managedNodeGroups.
Logs
Anything else we need to know?
Eksctl 0.108.0-dev+728d4ad1.2022-08-12T13:07:50Z on MacOS installed via brew
eksctl version: 0.108.0-dev+728d4ad1.2022-08-12T13:07:50Z
kubectl version: v1.24.3
OS: darwin
Hello andrei-dascalu :wave: Thank you for opening an issue in eksctl project. The team will review the issue and aim to respond within 1-3 business days. Meanwhile, please read about the Contribution and Code of Conduct guidelines here. You can find out more information about eksctl on our website
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 to run eksctl create nodegroup.
@cPu1 hi, thanks for the reply. I don't quite understand then how it's supposed to work with config.yaml
Config.yaml is supposed to provide a declarative way of configuring a cluster, right? If my first attempt fails, I would expect my second attempt (with a fixed configuration) to have a different result.
@andrei-dascalu your assumption is right, but eksctl seems to be designed in many ways so that a "happy path" run works like that, but every other case needs understanding what went wrong and how to fix it. eg. eksctl != terraform.
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.
This issue was closed because it has been stalled for 5 days with no activity.