This message was deleted.
# awss
sparse-intern-71089
07/07/2022, 6:59 PMThis message was deleted.
f
fresh-notebook-40503
07/07/2022, 7:00 PMbasically,
pulumi upMinimum number of live Pods was not attainedb
billowy-army-68599
07/07/2022, 7:18 PM
do the nodes get created in the same AWS account?
billowy-army-68599
07/07/2022, 7:18 PM
i've never seen anything like this before
f
flat-laptop-90489
07/07/2022, 7:54 PMI've had many different reasons that node groups don't end up getting attached to clusters. Outside of missing IAM roles, networking is a big one.
Usually though, I have to ssh to the node and go digging through boostrap script logs, kubelet logs, etc.
f
fresh-notebook-40503
07/07/2022, 8:45 PMthe nodes are successfully being created in the same AWS account, but they are not being associated with the eks cluster.
good call! I'll ssh into the created nodes and look through the logs there. thanks!
fresh-notebook-40503
07/07/2022, 9:22 PMah i think i've got it. the nodes can't reach the public API of the k8s cluster. the nodes are in a private subnet, and the route table for the private subnet has a 0.0.0.0/0 entry pointing to a NAT Gateway. Unfortunately, the NAT Gateway is in a private subnet. It needs to be in a public subnet with a 0.0.0.0/0 entry pointing to the internet gateway of the VPC
fresh-notebook-40503
07/07/2022, 9:28 PMgreat, that was the problem. all fixed. thanks for the help!
👍 1
31 Views