Closed xec-abailey closed 7 months ago
Thank you for opening this issue, we will look into it.
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @dyu1208, @FumingZhang, @andyliuliming.
We had the same issue. Turns out you most likely will need to run userAssignedNATGateway as you are doing BYO VNet.
@xec-abailey it's not supported to migrate the outbound type from loadBalancer to managedNATGateway if the cluster is using BYO vnet.
Describe the bug
Attempting to update a cluster (Kubernetes 1.28.3) to use managedNATGateway rather than default loadBalancer via the command:
az aks update -n cluster -g group --outbound-type managedNATGateway --nat-gateway-managed-outbound-ip-count 16
Which returns:
Invalid outbound type, supported values are loadBalancer, managedNATGateway, userAssignedNATGateway and userDefinedRouting.
Unsure as to the cause of this since the outbound type name is clearly the same.
Related command
az aks update -n cluster -g group --outbound-type managedNATGateway --nat-gateway-managed-outbound-ip-count 16
Errors
Invalid outbound type, supported values are loadBalancer, managedNATGateway, userAssignedNATGateway and userDefinedRouting.`
Issue script & Debug output
Expected behavior
As I have done on other clusters, I would expect this to update the outbound type and nat gateway outbound ip count accordingly.
Environment Summary
azure-cli 2.55.0
core 2.55.0 telemetry 1.1.0
Dependencies: msal 1.24.0b2 azure-mgmt-resource 23.1.0b2
Python location '/usr/local/pipx/venvs/azure-cli/bin/python' Extensions directory '/root/.azure/cliextensions'
Python (Linux) 3.11.7 (main, Dec 5 2023, 18:55:16) [GCC 12.2.0]
Additional context
No response