Chetan Patwal

@uchiha-pain, you do not need to provide those options, eksctl takes care of that when using the [fully-private clusters](https://eksctl.io/usage/eks-private-cluster/) feature. Head over to the documentation to find more details.

Can you share the events for the CloudFormation stack `eksctl-helix-cluster-nodegroup-ng-1`, using the AWS Console or via [aws cloudformation describe-stack-events](https://docs.aws.amazon.com/cli/latest/reference/cloudformation/describe-stack-events.html)? As a workaround, you can try deleting the CloudFormation stack `eksctl-helix-cluster-nodegroup-ng-1`...

@prasobhen, can you share your ClusterConfig file? This does look like a bug. We'll investigate the issue and get back to you soon.

eksctl does not attempt to ascertain if an AZ is supported in Fargate during cluster creation. But I do agree that the error message can be improved to guide the...

@maxinfosoft, do you have any logs you can share from the command? Can you confirm your kubectl is configured to use `my-cluster` and not some other cluster?

>The command ended without error messages. Logs would still aid us in debugging the issue. Please share the logs if you have them. Can you try deleting and recreating the...

This is indeed a bug in `eksctl create addon`. Instead of filtering out addons that already exist in the cluster, it's attempting to recreate them, resulting in a 409 error....

@skymoore, as a workaround, you can omit the existing addons from ClusterConfig and specify only `aws-ebs-csi-driver`, and run `create addon` again. ```yaml addons: - name: aws-ebs-csi-driver ```

> > @skymoore, as a workaround, you can omit the existing addons from ClusterConfig and specify only `aws-ebs-csi-driver`, and run `create addon` again. > > ```yaml > > addons: >...

> The work around not working for IPv6 cluster, I got: > > ```shell > Error: the default core addons must be defined for IPv6; missing addon(s): vpc-cni, coredns, kube-proxy...