In particular, there are cases where the pending state persists despite not running out of CPU or memory. There is a case that it is due to lack of private ip.If the node group is shown as "Degraded" in the EKS cluster configuration and you can see the following error in Health issues. "Amazon Autoscaling was unable to launch instances because there are not enough free addresses in the subnet associated with your AutoScaling group(s)." And you can see that the number of "Available IP4 addresses" in the AWS VPC subnet used in the node group is 0. By designating the IP that the node group occupies, you can get some IPs back. kubectl set env -n kube-system daemonset/aws-node MINIMUM_IP_TARGET=10 WARM_IP_TARGET=2 kubectl get daemonset -n kube-system aws-node -o json | jq -r '.spec.template.spec.containers[] |select ( .name == "aws-node" ).env' You can see that the number of "Available IP4 addresses" in the AWS VPC subnet is increa