EKS Worker-node join

0

Hi Guys,

I would like to start a standalone worker-node (with launch config, and ASG works correctly)
but when I make a copy (a launch template) from my launch config (with all the parameters that works with ASG) and start an instance manually , the node never join to the cluster.

I also ssh into this node and fire the bootstrap.sh with manually from the root console, but also nothing happen.

where can I see log or something, I would like to figure out why I am not able to start a single worker by my hand :)

Do you have any idea what is going on? what should I check?

Thanks,
Darvi

ps: My Target is to run a single node connected to my cluster with specific label and fix private IP in a subnet. So I can run my app as a daemonset (it is an IoT data collector / UDP, and I need the device IP from the network - so I cannot use NLB/UDP because every packet would come from the NLB's IP and that is not good for me ;( )

Darvi
已提問 5 年前檢視次數 289 次
1 個回答
0

I can answer my question!
The problem was the cluster tags on the ec2 instance

solution is to use this:
- Key: kubernetes.io/cluster/${ClusterName}
Value: owned

it comes from the CF template:
https://amazon-eks.s3-us-west-2.amazonaws.com/cloudformation/2019-02-11/amazon-eks-nodegroup.yaml

Regards,
Darvi

Darvi
已回答 5 年前

您尚未登入。 登入 去張貼答案。

一個好的回答可以清楚地回答問題並提供建設性的意見回饋,同時有助於提問者的專業成長。

回答問題指南