2 Respostas
- Mais recentes
- Mais votos
- Mais comentários
1
Hello there,
For managed nodes with custom AMI, the overrideBootstrapCommand is required. For unmanaged nodes overrideBootstrapCommand is recommended for AmazonLinux2 and Ubuntu custom images.
Don't use 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[0].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/
respondido há 2 anos
1
Check the CloudFormation stack "eksctl-test-cluster-nodegroup-serv-test-1", click events tab to view the error message why the node group failed.
respondido há 2 anos
It only gives this error
Resource handler returned message: "[Issue(Code=NodeCreationFailure, Message=Instances failed to join the kubernetes cluster, ResourceIds=[i-09a3d319c13a23f59])] (Service: null, Status Code: 0, Request ID: null)" (RequestToken: 16d9967f-ddfa-714b-8fe5-a1b97b10749b, HandlerErrorCode: GeneralServiceException)
Conteúdo relevante
- AWS OFICIALAtualizada há 2 anos
- AWS OFICIALAtualizada há 2 anos
- AWS OFICIALAtualizada há um ano
Hi @Olawale. I have tried the config that you mentioned above.
When I used the above config I got the following logs
The most annoying thing is that when I specify only ami instead of amiFamily it only uses [AmazonLinux2/1.23] not the Ubuntu. but as I am working behind the proxy so I also tried the following full command
But still it does not work