<p>I'm creating a new EKS Kubernetes Cluster on AWS.</p>

<p>When I deploy my workloads (migrating from an existing cluster) Kubelet stopps posting node status and all worker nodes become "NotReady" within a minute.</p>

<p>I was assuming that a misconfiguration within my cluster should not make the nodes crash - but apperently it does.</p>

<p>Can a misconfiguration within my cluster really make the AWS EKS Worker Nodes "NotReady"? Are there some rules of thumb under what circumstances this can happen? CPU Load to high? Pods in kube-system crashing? </p>

<p>This is a community wiki answer based on the solution from comments and posted for better visibility. Feel free to expand it.</p>
<p>As suggested by @gusto2 the problem was with the kubelet pod that was unable to call the API server. @stackoverflowjakob late confirmed that the connection between worker and master node was broken due to <a href="https://aws.amazon.com/vpc/?vpc-blogs.sort-by=item.additionalFields.createdDate&amp;vpc-blogs.sort-order=desc" rel="nofollow noreferrer">VPC</a> misconfiguration and it was discovered by checking <a href="https://aws.amazon.com/console/" rel="nofollow noreferrer">AWS Console</a> -&gt; EKS status.</p>
