question

DrFox-8730 avatar image
0 Votes"
DrFox-8730 asked srbose-msft edited

Problems upgrading cluster

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

azure-kubernetes-service
· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

@DrFox-8730 , 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:

  • they must be upgraded within one minor version of kube-apiserver before the control plane can be upgraded

  • it increases the likelihood of running kubelet versions older than the three maintained minor releases

0 Votes 0 ·

0 Answers