<p>I am trying to upgrade my kubernetes version from <code>1.14</code> to <code>1.15</code>, the cluster upgrade went well but when i am trying to update the node i am seeing the message
<code>Couldn't proceed with upgrade process as new nodes are not joining node group standard-workers . I had created the nodes using eksctl</code>.</p>
<p>I see the following error when i check the new node details under workloads.</p>
<pre><code>runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:docker: network plugin is not ready: cni config uninitialized
</code></pre>
<p>I also checked the tags associated with the new nodes getting spun up, they are all the same with one difference, the existing nodes have <code>aws:ec2launchtemplate:version</code> set to <code>1</code> and new nodes have it set to <code>4</code></p>
<p>I have checked the CNI plugin version and it corresponds to the latest once recommened</p>
<pre><code>kubectl describe daemonset aws-node --namespace kube-system | grep Image | cut -d &quot;/&quot; -f 2
amazon-k8s-cni-init:v1.7.5-eksbuild.1
amazon-k8s-cni:v1.7.5-eksbuild.1
</code></pre>
<p>Any help on how to get around this would be really helpfull.</p>
<p>TIA</p>

<p>for others visiting the post. I found out that the issue was the <code>url</code> i was using to configure the kube proxy.</p>
<p>As per the documentation <a href="https://docs.aws.amazon.com/eks/latest/userguide/update-cluster.html" rel="nofollow noreferrer">https://docs.aws.amazon.com/eks/latest/userguide/update-cluster.html</a>, it says</p>
<pre><code>Update kube-proxy to the recommended version by taking the output from the 
previous step and replacing the version tag with your cluster's recommended
 kube-proxy version:


kubectl set image daemonset.apps/kube-proxy \
    -n kube-system \
    kube-proxy=&lt;602401143452.dkr.ecr.us-west-2.amazonaws.com&gt;/eks/kube-proxy:v&lt;1.18.9&gt;-eksbuild.1

Your account ID and Region may differ from the example above.
</code></pre>
<p>I misunderstood the last part of account id and substituted it with my account id, which resulted in the image not getting found.</p>
<p>After using the correct link with account id <code>602401143452</code>, i was able to fix the issue and node group upgrade was successful.</p>
<p>Hope this helps, Thanks.</p>
