`az aks upgrade` doesn't work with azure network plugin
See original GitHub issueDescribe the bug
az aks upgrade
fails with the following error when used on a cluster that uses the azure
network plugin (custom vnet)
Operation failed with status: 'Bad Request'. Details: Changing property 'networkProfile.networkPlugin' is not allowed.
To Reproduce
- create an AKS cluster in a custom vnet
- run
az aks upgrade -k 1.9.6 -n aks -g vnet-aks
to upgrade the cluster
Expected behavior
The cluster to be upgraded, or possibly a no-op if it’s the same version
Environment summary
apt-get / 2.0.32 / Ubuntu 16.04 via WSL / zsh
Issue Analytics
- State:
- Created 5 years ago
- Reactions:4
- Comments:5 (1 by maintainers)
Top Results From Across the Web
Resolve issues when upgrading AKS hybrid - Microsoft Learn
This article describes known issues and errors you may encounter when upgrading Azure Kubernetes Service (AKS) hybrid deployments to the newest release.
Read more >Troubleshoot network problems in AKS clusters
Learn about steps to take to troubleshoot network problems in Azure Kubernetes Service (AKS) clusters.
Read more >Upgrade an Azure Kubernetes Service (AKS) cluster
Learn how to upgrade an Azure Kubernetes Service (AKS) cluster to get the latest features and security updates.
Read more >Troubleshoot the "SubnetIsFull" error code during an AKS ...
This article discusses how to identify and resolve the "SubnetIsFull" error that occurs when you try to upgrade an Azure Kubernetes Service (AKS)...
Read more >Resolve issues and errors during an AKS hybrid installation
This error may occur for users who have defined Azure Policies at a subscription or resource group level, and then attempt to install...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
There were a couple service-side issues relating to VNET upgrade that were fixed long ago–this is no longer an issue. @tjprescott this issue can be closed.
+1 same issue when trying to scale.