This message was deleted.
# general
s
This message was deleted.
c
Sounds like possibly IAM or Network. Maybe try get the status from the aws-node and kube-proxy pods:
Copy code
kubectl get pods -n kube-system -o wide
As per https://aws.amazon.com/premiumsupport/knowledge-center/eks-node-status-ready/
s
Yeah they are all running and scheduled on a node, can’t get the logs from them though
c
Smells like permissions error but I could be wrong
s
Yeah, that definitely seems plausible
f
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