For managed nodes with custom AMI, the overrideBootstrapCommand is required. For unmanaged nodes overrideBootstrapCommand is recommended for AmazonLinux2 and Ubuntu custom images.
amiFamily: Ubuntu2004, instead used
ami: ami-0feb1a4a4e739ea4e. You can get the latest Ubuntu image from https://cloud-images.ubuntu.com/aws-eks/. The
overrideBootstrapCommand can only be set when a custom AMI with
managedNodeGroups.ami is specified.
managedNodeGroups: - name: serv-test-1 ami: ami-0feb1a4a4e739ea4e instanceType: m5.xlarge overrideBootstrapCommand: | #!/bin/bash /etc/eks/bootstrap.sh <cluster-name>
For more, see https://eksctl.io/usage/custom-ami-support/
Check the CloudFormation stack "eksctl-test-cluster-nodegroup-serv-test-1", click events tab to view the error message why the node group failed.
Ubuntu nodes failed to join fully private clusterAccepted Answer
Ubuntu Managed Nodes creation failure in Fully-Private cluster
AWS Ubuntu Managed nodeGroup instances failing to join kubernetes cluster
Fully private eks clusterasked 3 months ago
What could be causing EKS nodes to fail to join a cluster on a specific account?asked 10 months ago
NodeCreationFailure - Instances failed to join the kubernetes clusterasked 5 months ago
Failed to setup parallel cluster on AWS EC2 with Ubuntu OS.asked 3 years ago
Why does my EKS cluster fails init on "Nodegroup... failed to stabilize"?asked 3 years ago
Instances failed to join the kubernetes clusterasked 2 years ago
EKS Managed Nodegroup with Capacity Reservation in Launch Template through CloudFormation does not use Capacity Reservation.asked 8 months ago