Verify NodeGroup subnets to confirm EC2 Instances are in Public Subnet
Verify the node group subnet to ensure it created in public subnets
Go to Services -> EKS -> eksdemo -> eksdemo1-ng1-public
Click on Associated subnet in Details tab
Click on Route Table Tab.
We should see that internet route via Internet Gateway (0.0.0.0/0 -> igw-xxxxxxxx)
Verify Cluster, NodeGroup in EKS Management Console
Go to Services -> Elastic Kubernetes Service -> eksdemo1
List Worker Nodes
# List EKS clusters
eksctl get cluster
# List NodeGroups in a cluster
eksctl get nodegroup --cluster=<clusterName>
# List Nodes in current kubernetes cluster
kubectl get nodes -o wide
# Our kubectl context should be automatically changed to new cluster
kubectl config view --minify
Verify Worker Node IAM Role and list of Policies
Go to Services -> EC2 -> Worker Nodes
Click on IAM Role associated to EC2 Worker Nodes
Verify Security Group Associated to Worker Nodes
Go to Services -> EC2 -> Worker Nodes
Click on Security Group associated to EC2 Instance which contains remote in the name.
Verify CloudFormation Stacks
Verify Control Plane Stack & Events
Verify NodeGroup Stack & Events
Login to Worker Node using Keypai kube-demo
Login to worker node
# For MAC or Linux or Windows10
ssh -i kube-demo.pem ec2-user@<Public-IP-of-Worker-Node>
# For Windows 7
Use putty
Step-06: Update Worker Nodes Security Group to allow all traffic
We need to allow All Traffic on worker node security group