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(22.400000000000002, 93%, 12%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAM%3C/text%3E%3C/svg%3E)
I encounter an error while upgrading AKS from version 1.14.8 to 1.15.11/12
Upgrade fails both using Azure Portal as well as Azure CLI
Details of the error are as follows:
Failed to save Kubernetes service. Error: The gateway did not receive a response from 'Microsoft.ContainerService' within the specified time period.
Screenshot attached for reference.
Hi Aalap,
Thanks for the Q&A question! The error you received typically implies a temporary issue. If you try to upgrade your AKS version now are you still receiving that same error?
AlapMhatre, are you still getting the same error?
I continue to receive this error even now.
I'm sorry to hear that. Give me some time to do some expanded research and I'll get back to you.
Hello,
Considering the end of support for Kubernetes versions 1.15, I am afraid this may impact my cluster upgrade activities as well.
Hope to have a resolution to this issue at the earliest.
Just a further note, another cluster within the same virtual network was successfully upgraded though.
Hey @Aalap Mhatre
At this point, I think this issue should be investigated by support. If you can email me at AzCommunity@Microsoft.com with Subject 'Attn: Winston' and provide your Subscription ID and link to this thread, I will enable a one-time free support request so you can work with a support engineer and get this sorted out and mitigated for good.
Thanks
Hi Winston,
Just mailed you the details. Hope this helps.
Thanks.
I was able to upgrade to cluster 1.15.11. I don’t know if this is the real cause, but the upgrade worked after I modified the read locks which were applied on the Network Monitoring & Container Insights SOLUTIONS linked to the log analytics workspaces.
I now have to do a subsequent upgrade to cluster 1.16.x