https://pulumi.com
Join Slack
This message was deleted.
# aws
s
This message was deleted.
f
basically, 
pulumi up
hangs for a while on "waiting for pods to be ready", and then I get errors like 
Minimum number of live Pods was not attained
. Makes sense - there are no nodes associated with the cluster. The default node group is not being created, even though the EC2 instances were created
b
do the nodes get created in the same AWS account?
i've never seen anything like this before
f
I'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
the 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!
ah 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
great, that was the problem. all fixed. thanks for the help!
👍 1
30 Views
Open in Slack
PreviousNext
Powered by

Pulumi Community

No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Powered by