<p>Per <a href="https://docs.aws.amazon.com/eks/latest/userguide/windows-support.html" rel="nofollow noreferrer">https://docs.aws.amazon.com/eks/latest/userguide/windows-support.html</a>, I ran the command, eksctl utils install-vpc-controllers --cluster &lt;cluster_name&gt; --approve</p>
<p>My EKS version is v1.16.3. I tries to deploy Windows docker images to a windows node. I got error below.</p>
<p>Warning  FailedCreatePodSandBox  31s               kubelet, ip-west-2.compute.internal  Failed create pod sandbox: rpc error: code = Unknown desc = failed to set up sandbox container &quot;ab8001f7b01f5c154867b7e&quot; network for pod &quot;mrestapi-67fb477548-v4njs&quot;: networkPlugin cni failed to set up pod &quot;mrestapi-67fb477548-v4njs_ui&quot; network: failed to parse Kubernetes args: pod does not have label vpc.amazonaws.com/PrivateIPv4Address</p>
<pre><code>$ kubectl logs vpc-resource-controller-645d6696bc-s5rhk -n kube-system
I1010 03:40:29.041761       1 leaderelection.go:185] attempting to acquire leader lease  kube-system/vpc-resource-controller...
I1010 03:40:46.453557       1 leaderelection.go:194] successfully acquired lease kube-system/vpc-resource-controller
W1010 23:57:53.972158       1 reflector.go:341] pkg/mod/k8s.io/client-go@v0.0.0-20180910083459-2cefa64ff137/tools/cache/reflector.go:99: watch of *v1.Pod ended with: too old resource version: 1480444 (1515040)
</code></pre>
<p>It complains too old resource version. How do I upgrade the version?</p>

<ol>
<li>I removed the windows nodes, re-created windows nodes with different instance type. But, it did not work.</li>
<li>Removed windows nodes group, re-created windows nodes group. It did not work.</li>
<li>Finally, I removed entire EKS cluster, re-created eks cluster. The command, kubectl describe node &lt;windows_node&gt; gives me the output below.</li>
</ol>
<pre><code>  vpc.amazonaws.com/CIDRBlock           0         0
  vpc.amazonaws.com/ENI                 0         0
  vpc.amazonaws.com/PrivateIPv4Address  1         1
</code></pre>
<p>Deployed windows-server-iis.yaml. It works as expected. The root cause of the problem is mystery.</p>
