[Bug]

[shankey28]

What were you trying to accomplish?

Create EKS cluster with unmanaged node group:

What happened?

The command completed successfully. cluster created nodegroup created and confirmed in cloudformation console. However I do not see nodegroup in the EKS console under cluster -> node group

How to reproduce it?

eksctl get nodegroup --cluster nginx-ingress-controller-walkthrough --region us-east-1

CLUSTER NODEGROUP STATUS CREATED MIN SIZE MAX SIZE DESIRED CAPACITY INSTANCE TYPE IMAGE ID ASG NAME TYPE nginx-ingress-controller-walkthrough ng-1 CREATE_COMPLETE 2024-05-04T06:24:12Z 1 1 1 t2.large ami-057f49c54d950e56c eksctl-nginx-ingress-controller-walkthrough-nodegroup-ng-1-NodeGroup-ADGZ9kPcgnEl unmanaged

However when I run below command. I get error:

aws eks describe-nodegroup --cluster-name nginx-ingress-controller-walkthrough --nodegroup-name ng-1 --region us-east-1

An error occurred (ResourceNotFoundException) when calling the DescribeNodegroup operation: No node group found for name: ng-1.

If using a config file, include it here, removing any sensitive information! -->

---

apiVersion: eksctl.io/v1alpha5 kind: ClusterConfig

metadata: name: nginx-ingress-controller-walkthrough region: us-east-1

vpc: id: "vpc-4545reere" # (optional, must match VPC ID used for each subnet below) cidr: "10.42.0.0/16" # (optional, must match CIDR used by the given VPC) subnets:

must provide 'private' and/or 'public' subnets by availability zone as shown

private:
  us-east-1a:
    id: "subnet-343435452fd"
    cidr: "10.42.96.0/19" # (optional, must match CIDR used by the given subnet)
  us-east-1b:
    id: "subnet-dfd3434334"
    cidr: "10.42.128.0/19" # (optional, must match CIDR used by the given subnet)

public:
  us-east-1a:
    id: "subnet-3434335"
    cidr: "10.42.0.0/19" # (optional, must match CIDR used by the given subnet)

  us-east-1b:
    id: "subnet-trrtr33434"
    cidr: "10.42.32.0/19" # (optional, must match CIDR used by the given subnet)

nodeGroups:

• name: ng-1 instanceType: t2.large desiredCapacity: 1 privateNetworking: true # if only 'Private' subnets are given, this must be enabled

Versions

$ eksctl info

eksctl version: 0.176.0 kubectl version: v1.24.7-eks-fb459a0 OS: linux

[github-actions[bot]]

Hello shankey28 :wave: Thank you for opening an issue in eksctl project. The team will review the issue and aim to respond within 1-5 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

[punkwalker]

@shankey28 Hi Shashi, According to the config, you are creating an Unmanaged Nodegroup. Therefore the EKS console or AWS CLI won’t show the Nodegroup as it meant for Managed Nodegroup. if you want to view the unmanaged nodegroup you can do so using eksctl as well as you can view it in AWS Autoscaling Group Console.

[shankey28]

Closing based on @punkwalker comment