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.

Pulumi Community

Sounds like possibly IAM or Network.

Maybe try get the status from the aws-node and kube-proxy pods:

```kubectl get pods -n kube-system -o wide```
As per <https://aws.amazon.com/premiumsupport/knowledge-center/eks-node-status-ready/>

Yeah they are all running and scheduled on a node, can’t get the logs from them though

Smells like permissions error but I could be wrong

Without kubelet logs and other bootstrapping logs from the nodes themselves, it will be very difficult to diagnose.

But agreed, networking or permissions both seem plausible