2 Answers
- Newest
- Most votes
- Most comments
1
Hello Jerome,
Kindly check this detailed guide- https://medium.com/@debolek4dem/guides-on-how-amazon-eks-cluster-operates-correctly-when-using-both-private-and-public-subnets-6ad54547c505
0
Basically you need to check logs(Kubelet) and communication between worker nodes and control plane. This is reason that cause the node in node ready state.
Please check following guides to troubleshoot this issues.
https://repost.aws/knowledge-center/eks-worker-node-not-ready
answered 23 days ago
Relevant content
- Accepted Answerasked 9 months ago
- asked a year ago
- asked 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 12 days ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 5 months ago