Unable to see node group

malavsandeep · August 3, 2026, 7:20pm

followed document step by step

kodekloudhub/certified-kubernetes-administrator-course/blob/master/managed-clusters/eks/console/docs/07-join-nodes.md

# Join Worker Nodes

Now that CloudFormation has created the EC2 instances for the worker nodes, we need to join them to the cluster. Once again, if this is a lab or KKE task, the following must be done at the *lab* terminal.

1. Return to the CloudShell terminal. If you closed it, press the button at the top to reopen it. If it tells you the session is closed due to inactivity, hit Enter to restart it.
1. Download the node configmap

    ```
    curl -O https://s3.us-west-2.amazonaws.com/amazon-eks/cloudformation/2020-10-29/aws-auth-cm.yaml
    ```
1. Now edit it in `vi`

    ```
    vi aws-auth-cm.yaml
    ```

    Where it says `rolearn: <ARN of instance role (not instance profile)>`, you need to delete `<ARN of instance role (not instance profile)>` and paste in the value for `NodeInstanceRole` you got from the previous section. When you are done, it should look something like this (though the actual value will be different for you).

    ```yaml
    apiVersion: v1

This file has been truncated. show original

rob_kodekloud · August 3, 2026, 11:51pm

I’m walking through the tutorial right now. It’s actually working for me:

vim aws-auth-cm.yaml
~ $ kubectl apply -f aws-auth-cm.yaml
configmap/aws-auth created
~ $ kubectl get nodes
NAME                            STATUS     ROLES    AGE   VERSION
ip-172-31-1-181.ec2.internal    NotReady   <none>   23s   v1.24.17-eks-59bf375
ip-172-31-8-74.ec2.internal     NotReady   <none>   18s   v1.24.17-eks-59bf375
ip-172-31-89-145.ec2.internal   NotReady   <none>   23s   v1.24.17-eks-59bf375
~ $ kubectl get nodes
NAME                            STATUS     ROLES    AGE   VERSION
ip-172-31-1-181.ec2.internal    NotReady   <none>   70s   v1.24.17-eks-59bf375
ip-172-31-8-74.ec2.internal     Ready      <none>   65s   v1.24.17-eks-59bf375
ip-172-31-89-145.ec2.internal   Ready      <none>   70s   v1.24.17-eks-59bf375
~ $ kubectl get nodes
NAME                            STATUS   ROLES    AGE   VERSION
ip-172-31-1-181.ec2.internal    Ready    <none>   75s   v1.24.17-eks-59bf375
ip-172-31-8-74.ec2.internal     Ready    <none>   70s   v1.24.17-eks-59bf375
ip-172-31-89-145.ec2.internal   Ready    <none>   75s   v1.24.17-eks-59bf375
~ $ kubectl get po -A
NAMESPACE      NAME                              READY   STATUS    RESTARTS     AGE
external-dns   external-dns-76b5567444-65pdt     1/1     Running   0            22m
kube-system    aws-node-8sgn2                    2/2     Running   0            88s
kube-system    aws-node-hvcbs                    2/2     Running   0            83s
kube-system    aws-node-phk5l                    2/2     Running   0            88s
kube-system    coredns-b8b6dd877-cxdg9           1/1     Running   0            22m
kube-system    coredns-b8b6dd877-zmzxz           1/1     Running   0            22m
kube-system    eks-node-monitoring-agent-f42q9   1/1     Running   1 (9s ago)   88s
kube-system    eks-node-monitoring-agent-g95c5   1/1     Running   0            88s
kube-system    eks-node-monitoring-agent-gh6sf   1/1     Running   0            83s
kube-system    eks-pod-identity-agent-4ljjx      1/1     Running   0            88s
kube-system    eks-pod-identity-agent-x5b48      1/1     Running   0            83s
kube-system    eks-pod-identity-agent-xfmdv      1/1     Running   0            88s
kube-system    kube-proxy-rv8t5                  1/1     Running   0            88s
kube-system    kube-proxy-w9s9b                  1/1     Running   0            83s
kube-system    kube-proxy-z7mt6                  1/1     Running   0            88s
kube-system    metrics-server-5f8959cc48-6hnhz   1/1     Running   0            25m
kube-system    metrics-server-5f8959cc48-hhxq7   1/1     Running   0            25m
~ $

If I had to guess, you may not have made the correct edit to the configmap. But in general, the totorial seems to work.