<p>I’m getting an error when using terraform to provision node group on AWS EKS.
Error: error waiting for EKS Node Group (xxx) creation: <code>NodeCreationFailure: Unhealthy nodes in the kubernetes cluster.</code></p>
<p>And I went to console and inspected the node. There is a message <code>“runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:docker network plugin is not ready: cni config uninitialized”</code>.</p>
<p>I have 5 private subnets and connect to Internet via NAT.</p>
<p>Is someone able to give me some hint on how to debug this?</p>
<p>Here are some details on my env.</p>
<pre><code>Kubernetes version: 1.18
Platform version: eks.3
AMI type: AL2_x86_64
AMI release version: 1.18.9-20201211
Instance types: m5.xlarge
</code></pre>
<p>There are three workloads set up in the cluster.</p>
<pre><code>coredns, STATUS (2 Desired, 0 Available, 0 Ready)
aws-node STATUS (5 Desired, 5 Scheduled, 0 Available, 0 Ready) 
kube-proxy STATUS (5 Desired, 5 Scheduled, 5 Available, 5 Ready)
</code></pre>
<p>go inside the <code>coredns</code>, both pods are in pending state, and conditions has <code>“Available=False, Deployment does not have minimum availability”</code> and <code>“Progress=False, ReplicaSet xxx has timed out progressing”</code>
go inside the one of the pod in <code>aws-node</code>, the status shows <code>“Waiting - CrashLoopBackOff”</code></p>

<p>Add pod network add-on</p>
<pre><code>kubectl apply -f https://raw.githubusercontent.com/coreos/flannel/2140ac876ef134e0ed5af15c65e414cf26827915/Documentation/kube-flannel.yml
</code></pre>
