This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(41.6, 57.00000000000001%, 14%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDF%3C/text%3E%3C/svg%3E)
Hi
Currently trying to upgrade a cluster from 1.17.16 to 1.18.19 and things have got into a bit of a loop.
It seems my nodepool version is out of step from the cluster version and is back on 1.15.5
When I try to upgrade the control plane and nodepool or just the control plane I get an error message telling me that the cluster is too far behind (it can only be 2 minor versions behind)
When I try to upgrade the nodepool directly it says that 1.17.6 is no longer supported and cant be upgraded to.
I cant add a nodepool for the same reason that 1.17.16 is no longer supported and I cant remove the existing nodepool as it is the only one.
This happens through both the UI and az aks commands
Any help on how I can get out of this mess would be appreciated.
Thanks
@Dr Fox , Thank you for your question.
This certainly is tricky. The Kubernetes version skew policy " kubelet must not be newer than kube-apiserver, and may be up to two minor versions older" has your cluster at odds.
The best course of action would be to open a technical support request with us so that our engineers can help fix this manually.
----------
Running a cluster with kubelet instances that are persistently two minor versions behind kube-apiserver is not recommended:
kube-apiserver before the control plane can be upgraded kubelet versions older than the three maintained minor releases