search

Azure / azure-cli

Azure Command-Line Interface
MIT License
3.97k stars 2.95k forks source link

AKS command update not working with --api-server-authorized-ip-ranges parameter set to "" #16505

Open niswitze opened 3 years ago

niswitze commented 3 years ago

az feedback auto-generates most of the information requested below, as of CLI version 2.0.62

Describe the bug Currently, the parameter for removing authorized ip ranges for the Kubernetes API Server in the AZ CLI does not work. The public and CLI documentation state to set the parameter --api-server-authorized-ip-ranges to "" and that will set the authorizedIpRanges field to null. Performing this just causes a bad syntax error to occur. The only way to get around this is to directly set the parameter to "" using an = sign

To Reproduce

  1. Create or already have an AKS cluster with API Server Authorized IP Ranges set
  2. Try to remove these ranges using the documented syntax below. The following error should occur:

Expected behavior

Documented way that fails -> az aks update -g rgName -n clusterName --api-server-authorized-ip-ranges ""

Way that succeeds -> az aks update -g rgName -n clsuterName --api-server-authorized-ip-ranges=""

Environment summary Running from Windows PowerShell with the following CLI version:

{ "azure-cli": "2.17.1", "azure-cli-core": "2.17.1", "azure-cli-telemetry": "1.0.6", "extensions": { "alertsmanagement": "0.1.0", "azure-devops": "0.18.0", "azure-iot": "0.10.8", "costmanagement": "0.1.0", "interactive": "0.4.4", "resource-graph": "1.1.0" } }

ghost commented 3 years ago

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @Azure/aks-pm.

Issue Details
> ### `az feedback` auto-generates most of the information requested below, as of CLI version 2.0.62 **Describe the bug** Currently, the parameter for removing authorized ip ranges for the Kubernetes API Server in the AZ CLI does not work. The public and CLI documentation state to set the parameter --api-server-authorized-ip-ranges to "" and that will set the authorizedIpRanges field to null. Performing this just causes a bad syntax error to occur. The only way to get around this is to directly set the parameter to "" using an = sign **To Reproduce** 1. Create or already have an AKS cluster with API Server Authorized IP Ranges set 2. Try to remove these ranges using the documented syntax below. The following error should occur: **Expected behavior** Documented way that fails -> az aks update -g rgName -n clusterName --api-server-authorized-ip-ranges "" Way that succeeds -> az aks update -g rgName -n clsuterName --api-server-authorized-ip-ranges="" **Environment summary** Running from Windows PowerShell with the following CLI version: { "azure-cli": "2.17.1", "azure-cli-core": "2.17.1", "azure-cli-telemetry": "1.0.6", "extensions": { "alertsmanagement": "0.1.0", "azure-devops": "0.18.0", "azure-iot": "0.10.8", "costmanagement": "0.1.0", "interactive": "0.4.4", "resource-graph": "1.1.0" } }
Author: niswitze
Assignees: -
Labels: `AKS`, `Service Attention`, `needs-triage`
Milestone: -
yonzhan commented 3 years ago

aks

niswitze commented 3 years ago

@Azure/aks-pm @yonzhan

Has there been any update on this issue? Still facing this after updating to the latest AZ CLI version, 2.18.0.

yonzhan commented 3 years ago

This issue should be looked into by AKS service team.

niswitze commented 3 years ago

This issue should be looked into by AKS service team.

Got it, would it be possible to assign the issue to the team directly?

yonzhan commented 3 years ago

routing this to the appropriate team for follow-up. cc @Azure/aks-pm