2 個答案
- 最新
- 最多得票
- 最多評論
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/
已回答 1 年前
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.
已回答 1 年前
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)
相關內容
- 已提問 5 個月前
- AWS 官方已更新 7 個月前
- AWS 官方已更新 1 年前
- AWS 官方已更新 2 年前
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