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(70.4, 38%, 16%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EHW%3C/text%3E%3C/svg%3E)
We have a couple of AKS systems running on a deprecated version of Kubernetes (1.21) and could use some help in the upgrade process. The person who originally set this up 5 years ago is no longer with our firm. The configuration is managed by Helm files.
We have a Sandbox which can be used to test the upgrade process. We have a reasonable idea of what's invovled, but could use a guiding hand in the process so we don't go down a rabbit hole.
I suspect this would involve about 4 hours of paid consultation. Can we contract directly with an Azure employee to help us? If so, whom to we contact?
![](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(291.2, 38%, 38%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMP%3C/text%3E%3C/svg%3E)
The upgrade process is well documented and relatively straightforward. Follow https://learn.microsoft.com/en-us/azure/aks/upgrade-aks-cluster?tabs=azure-cli
If the above response helps answer your question, remember to "Accept Answer" so that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.
hth
Marcin
Marcin -- Thanks so much for your comments! The instructions do seem complete, but let me describe what happened to one of our prior IT teams when the tried to upgrade a third cluster running on 1.21. The upgrade ran and updated Kb8 to 1.25.15. But the cluster stopped working immediately. The problem seemed to be a version mis-matched between Kb8 and the Nginx-Ingress controller. The solution (sadly, poorly documented) required a manual upgrade of that controller. That process changed the external IP address of the cluster so DNS changes had to be made. With all of these changes made, our test server finally ran again. I just don't know the details of the manual nginx-ingress upgrade.
I have found references which indicate updating Nginx_Ingres requires cleaning out "hidden" supporting services and webhooks to start with. But I'm not sure they are complete.
I suspect that we wouldn't be running into this issue if we were upgrading from a later version. than 1.21.
Another mystery is that the working systems have two distinct ngnix-ingress modules. One is clearly the load balancer with the public IP address. We aren't sure what the second module does, or even if it's required.
So that's why I'm looking for an Azure paid consultant who lives and breathes helm and aks. It will be easy for her or him I'm sure as our overall system is not that complex.
![](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(76.8, 74%, 17%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAN%3C/text%3E%3C/svg%3E)
Hello Harry Whitehouse,
Support team will be able to help on this. I would recommend you to open a azure support case. If you don't have a support plan enabled on your subscription, I request you to send an email to AzCommunity@Microsoft.com with Subject as "Attn:Vikas" referencing this thread along with your subscription ID. He can then enable your subscription with a one-time free technical support. Once the issue is resolved, request you to post the resolution here for the benefit of community.
Thank you Anveshreddy. We do have an Azure support contract so I'll open a case. A minor update on the dual ingress controllers: They appear to be duplicates and one can specify the number you want running in a Helm config file. It provides additional routing capacity if loads are anticipated to be high. The way they are shown in AKS UI doesn't underscore that fact.