question

ArashNiknafs-0051 avatar image
0 Votes"
ArashNiknafs-0051 asked prmanhas-MSFT commented

Kubernete upgrade to 1.18.19 fails

Hi,

First I tried from the UI in Azure portal. I went through however after that I started seeing this error message:

110794-image.png

But when I check the container registry everything looks normal.

Does this mean the AKS is upgraded or not?

I also see this in the CL

110784-image.png


azure-kubernetes-serviceazure-container-registry
image.png (3.5 KiB)
image.png (43.6 KiB)
· 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.

@ArashNiknafs-0051 Any update on the issue?

Please "Accept as Answer" if below helped so it can help others in community looking for help on similar topics.

Thanks

0 Votes 0 ·

1 Answer

prmanhas-MSFT avatar image
1 Vote"
prmanhas-MSFT answered prmanhas-MSFT edited

@ArashNiknafs-0051 Thank you for your query!!!

Your AKS is not upgraded yet since if it was updates the result would be something as below same is mentioned here

110809-image.png

Until the cluster is out of failed state, upgrade and scale operations won't succeed.

As mentioned here below steps might help:

Common root issues and resolutions include:
- Scaling with insufficient compute (CRP) quota. To resolve, first scale your cluster back to a stable goal state within quota. Then follow these steps to request a compute quota increase before trying to scale up again beyond initial quota limits.
- Scaling a cluster with advanced networking and insufficient subnet (networking) resources. To resolve, first scale your cluster back to a stable goal state within quota. Then follow these steps to request a resource quota increase before trying to scale up again beyond initial quota limits.

Once the underlying cause for upgrade failure is resolved, your cluster should be in a succeeded state. Once a succeeded state is verified, retry the original operation.

Also you can ensure that any PodDisruptionBudgets (PDBs) is allowed for at least 1 pod replica to be moved at a time otherwise the drain/evict operation will fail. If the drain operation fails, the upgrade operation will fail by design to ensure that the applications are not disrupted. Please correct what caused the operation to stop (incorrect PDBs, lack of quota, and so on) and re-try the operation

Also, you can check activity logs of the AKS cluster. There will be a failed upgrade. The error message might help us to determine the correct reason as well if above is not the case.

Hope it helps!!!

Please "Accept as Answer" if it helped so it can help others in community looking for help on similar topics.




image.png (19.7 KiB)
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.