Merge pull request #275317 from schaffererin/updateparams5

Updated command parameters with long-form formatting

Author: prmerger-automator[bot]

articles/aks/api-server-vnet-integration.md

@@ -75,17 +75,17 @@ You can configure your AKS clusters with API Server VNet Integration in managed
 * Create a resource group using the [`az group create`][az-group-create] command.
 
     ```azurecli-interactive
-    az group create -l westus2 -n <resource-group>
+    az group create --location westus2 --name <resource-group>
     ```
 
 ### Deploy a public cluster
 
 * Deploy a public AKS cluster with API Server VNet integration for managed VNet using the [`az aks create`][az-aks-create] command with the `--enable-api-server-vnet-integration` flag.
 
     ```azurecli-interactive
-    az aks create -n <cluster-name> \
-        -g <resource-group> \
-        -l <location> \
+    az aks create --name <cluster-name> \
+        --resource-group <resource-group> \
+        --location <location> \
         --network-plugin azure \
         --enable-apiserver-vnet-integration
     ```
@@ -95,9 +95,9 @@ You can configure your AKS clusters with API Server VNet Integration in managed
 * Deploy a private AKS cluster with API Server VNet integration for managed VNet using the [`az aks create`][az-aks-create] command with the `--enable-api-server-vnet-integration` and `--enable-private-cluster` flags.
 
     ```azurecli-interactive
-    az aks create -n <cluster-name> \
-        -g <resource-group> \
-        -l <location> \
+    az aks create --name <cluster-name> \
+        --resource-group <resource-group> \
+        --location <location> \
         --network-plugin azure \
         --enable-private-cluster \
         --enable-apiserver-vnet-integration
@@ -117,24 +117,24 @@ The cluster identity needs permissions to both the API server subnet and the nod
 * Create a resource group using the [`az group create`][az-group-create] command.
 
 ```azurecli-interactive
-az group create -l <location> -n <resource-group>
+az group create --location <location> --name <resource-group>
 ```
 
 ### Create a virtual network
 
 1. Create a virtual network using the [`az network vnet create`][az-network-vnet-create] command.
 
     ```azurecli-interactive
-    az network vnet create -n <vnet-name> \
-    -g <resource-group> \
-    -l <location> \
+    az network vnet create --name <vnet-name> \
+    --resource-group <resource-group> \
+    --location <location> \
     --address-prefixes 172.19.0.0/16
     ```
 
 2. Create an API server subnet using the [`az network vnet subnet create`][az-network-vnet-subnet-create] command.
 
     ```azurecli-interactive
-    az network vnet subnet create -g <resource-group> \
+    az network vnet subnet create --resource-group <resource-group> \
     --vnet-name <vnet-name> \
     --name <apiserver-subnet-name> \
     --delegations Microsoft.ContainerService/managedClusters \
@@ -144,7 +144,7 @@ az group create -l <location> -n <resource-group>
 3. Create a cluster subnet using the [`az network vnet subnet create`][az-network-vnet-subnet-create] command.
 
     ```azurecli-interactive
-    az network vnet subnet create -g <resource-group> \
+    az network vnet subnet create --resource-group <resource-group> \
     --vnet-name <vnet-name> \
     --name <cluster-subnet-name> \
     --address-prefixes 172.19.1.0/24
@@ -155,7 +155,7 @@ az group create -l <location> -n <resource-group>
 1. Create a managed identity using the [`az identity create`][az-identity-create] command.
 
     ```azurecli-interactive
-    az identity create -g <resource-group> -n <managed-identity-name> -l <location>
+    az identity create --resource-group <resource-group> --name <managed-identity-name> --location <location>
     ```
 
 2. Assign the Network Contributor role to the API server subnet using the [`az role assignment create`][az-role-assignment-create] command.
@@ -179,9 +179,9 @@ az group create -l <location> -n <resource-group>
 * Deploy a public AKS cluster with API Server VNet integration using the [`az aks create`][az-aks-create] command with the `--enable-api-server-vnet-integration` flag.
 
     ```azurecli-interactive
-    az aks create -n <cluster-name> \
-    -g <resource-group> \
-    -l <location> \
+    az aks create --name <cluster-name> \
+    --resource-group <resource-group> \
+    --location <location> \
     --network-plugin azure \
     --enable-apiserver-vnet-integration \
     --vnet-subnet-id <cluster-subnet-resource-id> \
@@ -194,9 +194,9 @@ az group create -l <location> -n <resource-group>
 * Deploy a private AKS cluster with API Server VNet integration using the [`az aks create`][az-aks-create] command with the `--enable-api-server-vnet-integration` and `--enable-private-cluster` flags.
 
     ```azurecli-interactive
-    az aks create -n <cluster-name> \
-    -g <resource-group> \
-    -l <location> \
+    az aks create --name <cluster-name> \
+    --resource-group <resource-group> \
+    --location <location> \
     --network-plugin azure \
     --enable-private-cluster \
     --enable-apiserver-vnet-integration \
@@ -217,8 +217,8 @@ This upgrade performs a node-image version upgrade on all node pools and restart
 * Update your cluster to API Server VNet Integration using the [`az aks update`][az-aks-update] command with the `--enable-apiserver-vnet-integration` flag.
 
     ```azurecli-interactive
-    az aks update -n <cluster-name> \
-    -g <resource-group> \
+    az aks update --name <cluster-name> \
+    --resource-group <resource-group> \
     --enable-apiserver-vnet-integration \
     --apiserver-subnet-id <apiserver-subnet-resource-id>
     ```
@@ -235,8 +235,8 @@ AKS clusters configured with API Server VNet Integration can have public network
 * Enable private cluster mode using the [`az aks update`][az-aks-update] command with the `--enable-private-cluster` flag.
 
     ```azurecli-interactive
-    az aks update -n <cluster-name> \
-    -g <resource-group> \
+    az aks update --name <cluster-name> \
+    --resource-group <resource-group> \
     --enable-private-cluster
     ```
 
@@ -245,8 +245,8 @@ AKS clusters configured with API Server VNet Integration can have public network
 * Disable private cluster mode using the [`az aks update`][az-aks-update] command with the `--disable-private-cluster` flag.
 
     ```azurecli-interactive
-    az aks update -n <cluster-name> \
-    -g <resource-group> \
+    az aks update --name <cluster-name> \
+    --resource-group <resource-group> \
     --disable-private-cluster
     ```
 
@@ -255,7 +255,7 @@ AKS clusters configured with API Server VNet Integration can have public network
 * Configure `kubectl` to connect to your cluster using the [`az aks get-credentials`][az-aks-get-credentials] command.
 
     ```azurecli-interactive
-    az aks get-credentials -g <resource-group> -n <cluster-name>
+    az aks get-credentials --resource-group <resource-group> --name <cluster-name>
     ```
 
 ## Next steps

articles/aks/app-routing-dns-ssl.md

@@ -35,7 +35,7 @@ To connect to the Kubernetes cluster from your local computer, you use `kubectl`
 Configure kubectl to connect to your Kubernetes cluster using the [`az aks get-credentials`][az-aks-get-credentials] command.
 
 ```azurecli-interactive
-az aks get-credentials -g <ResourceGroupName> -n <ClusterName>
+az aks get-credentials --resource-group <ResourceGroupName> --name <ClusterName>
 ```
 
 ## Terminate HTTPS traffic with certificates from Azure Key Vault
@@ -52,7 +52,7 @@ To enable support for HTTPS traffic, see the following prerequisites:
 Create an Azure Key Vault using the [`az keyvault create`][az-keyvault-create] command.
 
 ```azurecli-interactive
-az keyvault create -g <ResourceGroupName> -l <Location> -n <KeyVaultName> --enable-rbac-authorization true
+az keyvault create --resource-group <ResourceGroupName> --location <Location> --name <KeyVaultName> --enable-rbac-authorization true
 ```
 
 ### Create and export a self-signed SSL certificate
@@ -79,7 +79,7 @@ For testing, you can use a self-signed public certificate instead of a Certifica
 Import the SSL certificate into Azure Key Vault using the [`az keyvault certificate import`][az-keyvault-certificate-import] command. If your certificate is password protected, you can pass the password through the `--password` flag.
 
 ```azurecli-interactive
-az keyvault certificate import --vault-name <KeyVaultName> -n <KeyVaultCertificateName> -f aks-ingress-tls.pfx [--password <certificate password if specified>]
+az keyvault certificate import --vault-name <KeyVaultName> --name <KeyVaultCertificateName> --file aks-ingress-tls.pfx [--password <certificate password if specified>]
 ```
 
 > [!IMPORTANT]
@@ -103,7 +103,7 @@ KEYVAULTID=$(az keyvault show --name <KeyVaultName> --query "id" --output tsv)
 Then update the app routing add-on to enable the Azure Key Vault secret store CSI driver and apply the role assignment.
 
 ```azurecli-interactive
-az aks approuting update -g <ResourceGroupName> -n <ClusterName> --enable-kv --attach-kv ${KEYVAULTID}
+az aks approuting update --resource-group <ResourceGroupName> --name <ClusterName> --enable-kv --attach-kv ${KEYVAULTID}
 ```
 
 ## Enable Azure DNS integration
@@ -121,7 +121,7 @@ To enable support for DNS zones, review the following prerequisite:
 1. Create an Azure DNS zone using the [`az network dns zone create`][az-network-dns-zone-create] command.
 
     ```azurecli-interactive
-    az network dns zone create -g <ResourceGroupName> -n <ZoneName>
+    az network dns zone create --resource-group <ResourceGroupName> --name <ZoneName>
     ```
 
 ### Attach Azure DNS zone to the application routing add-on
@@ -132,13 +132,13 @@ To enable support for DNS zones, review the following prerequisite:
 1. Retrieve the resource ID for the DNS zone using the [`az network dns zone show`][az-network-dns-zone-show] command and set the output to a variable named *ZONEID*.
 
     ```azurecli-interactive
-    ZONEID=$(az network dns zone show -g <ResourceGroupName> -n <ZoneName> --query "id" --output tsv)
+    ZONEID=$(az network dns zone show --resource-group <ResourceGroupName> --name <ZoneName> --query "id" --output tsv)
     ```
 
 1. Update the add-on to enable the integration with Azure DNS using the [`az aks approuting zone`][az-aks-approuting-zone] command. You can pass a comma-separated list of DNS zone resource IDs.
 
     ```azurecli-interactive
-    az aks approuting zone add -g <ResourceGroupName> -n <ClusterName> --ids=${ZONEID} --attach-zones
+    az aks approuting zone add --resource-group <ResourceGroupName> --name <ClusterName> --ids=${ZONEID} --attach-zones
     ```
 
 ## Create the Ingress that uses a host name and a certificate from Azure Key Vault
@@ -148,7 +148,7 @@ The application routing add-on creates an Ingress class on the cluster named *we
 1. Get the certificate URI to use in the Ingress from Azure Key Vault using the [`az keyvault certificate show`][az-keyvault-certificate-show] command.
 
     ```azurecli-interactive
-    az keyvault certificate show --vault-name <KeyVaultName> -n <KeyVaultCertificateName> --query "id" --output tsv
+    az keyvault certificate show --vault-name <KeyVaultName> --name <KeyVaultCertificateName> --query "id" --output tsv
     ```
 
    The following example output shows the certificate URI returned from the command:

articles/aks/app-routing-migration.md

@@ -25,7 +25,7 @@ In this article, you learn how to migrate your Azure Kubernetes Service (AKS) cl
 1. Enable the application routing add-on.
 
     ```azurecli-interactive
-    az aks approuting enable -g <ResourceGroupName> -n <ClusterName>
+    az aks approuting enable --resource-group <ResourceGroupName> --name <ClusterName>
     ```
 
 2. Update your Ingresses, setting `ingressClassName` to `webapprouting.kubernetes.azure.com`. Remove the `kubernetes.io/ingress.class` annotation. You also need to update the host to one that you own, as the application routing add-on doesn't have a managed cluster DNS zone. If you don't have a DNS zone, follow instructions to [create][app-routing-dns-create] and [configure][app-routing-dns-configure] one.
@@ -84,7 +84,7 @@ In this article, you learn how to migrate your Azure Kubernetes Service (AKS) cl
 4. Disable the HTTP application routing add-on.
 
     ```azurecli-interactive
-    az aks disable-addons -g <ResourceGroupName> -n <ClusterName> --addons http_application_routing
+    az aks disable-addons --resource-group <ResourceGroupName> --name <ClusterName> --addons http_application_routing
     ```
 
 ## Remove and delete all HTTP application routing resources

articles/aks/app-routing-nginx-configuration.md

@@ -25,7 +25,7 @@ To connect to the Kubernetes cluster from your local computer, you use `kubectl`
 Configure kubectl to connect to your Kubernetes cluster using the [`az aks get-credentials`][az-aks-get-credentials] command.
 
 ```azurecli-interactive
-az aks get-credentials -g <ResourceGroupName> -n <ClusterName>
+az aks get-credentials -resource-group <ResourceGroupName> --name <ClusterName>
 ```
 
 ## Configuration of the NGINX ingress controller

articles/aks/app-routing.md

@@ -54,15 +54,15 @@ With the retirement of [Open Service Mesh][open-service-mesh-docs] (OSM) by the
 To enable application routing on a new cluster, use the [`az aks create`][az-aks-create] command, specifying the `--enable-app-routing` flag.
 
 ```azurecli-interactive
-az aks create -g <ResourceGroupName> -n <ClusterName> -l <Location> --enable-app-routing
+az aks create --resource-group <ResourceGroupName> --name <ClusterName> --location <Location> --enable-app-routing
 ```
 
 ### Enable on an existing cluster
 
 To enable application routing on an existing cluster, use the [`az aks approuting enable`][az-aks-approuting-enable] command.
 
 ```azurecli-interactive
-az aks approuting enable -g <ResourceGroupName> -n <ClusterName>
+az aks approuting enable --resource-group <ResourceGroupName> --name <ClusterName>
 ```
 
 # [Open Service Mesh (OSM) (retired)](#tab/with-osm)
@@ -79,16 +79,16 @@ The following add-ons are required to support this configuration:
 Enable application routing on a new AKS cluster using the [`az aks create`][az-aks-create] command specifying the `--enable-app-routing` flag and the `--enable-addons` parameter with the `open-service-mesh` add-on:
 
 ```azurecli-interactive
-az aks create -g <ResourceGroupName> -n <ClusterName> -l <Location> --enable-app-routing --enable-addons open-service-mesh 
+az aks create --resource-group <ResourceGroupName> --name <ClusterName> --location <Location> --enable-app-routing --enable-addons open-service-mesh 
 ```
 
 ### Enable on an existing cluster
 
 To enable application routing on an existing cluster, use the [`az aks approuting enable`][az-aks-approuting-enable] command and the [`az aks enable-addons`][az-aks-enable-addons] command with the `--addons` parameter set to `open-service-mesh`:
 
 ```azurecli-interactive
-az aks approuting enable -g <ResourceGroupName> -n <ClusterName>
-az aks enable-addons -g <ResourceGroupName> -n <ClusterName> --addons open-service-mesh
+az aks approuting enable --resource-group <ResourceGroupName> --name <ClusterName>
+az aks enable-addons --resource-group <ResourceGroupName> --name <ClusterName> --addons open-service-mesh
 ```
 
 > [!NOTE]
@@ -104,15 +104,15 @@ az aks enable-addons -g <ResourceGroupName> -n <ClusterName> --addons open-servi
 To enable application routing on a new cluster, use the [`az aks create`][az-aks-create] command, specifying `--enable-app-routing` flag.
 
 ```azurecli-interactive
-az aks create -g <ResourceGroupName> -n <ClusterName> -l <Location> --enable-app-routing
+az aks create --resource-group <ResourceGroupName> --name <ClusterName> --location <Location> --enable-app-routing
 ```
 
 ### Enable on an existing cluster
 
 To enable application routing on an existing cluster,  use the [`az aks approuting enable`][az-aks-approuting-enable] command:
 
 ```azurecli-interactive
-az aks approuting enable -g <ResourceGroupName> -n <ClusterName>
+az aks approuting enable --resource-group <ResourceGroupName> --name <ClusterName>
 ```
 
 ---
@@ -124,7 +124,7 @@ To connect to the Kubernetes cluster from your local computer, you use [kubectl]
 Configure `kubectl` to connect to your Kubernetes cluster using the [az aks get-credentials][az-aks-get-credentials] command.
 
 ```azurecli-interactive
-az aks get-credentials -g <ResourceGroupName> -n <ClusterName>
+az aks get-credentials --resource-group <ResourceGroupName> -name <ClusterName>
 ```
 
 ## Deploy an application

articles/aks/configure-kube-proxy.md

@@ -110,10 +110,10 @@ You can view the full `kube-proxy` configuration structure in the [AKS Cluster S
 
     ```azurecli-interactive
     # Create a new cluster
-    az aks create -g <resourceGroup> -n <clusterName> --kube-proxy-config kube-proxy.json
+    az aks create --resource-group <resourceGroup> --name <clusterName> --kube-proxy-config kube-proxy.json
 
     # Update an existing cluster
-    az aks update -g <resourceGroup> -n <clusterName> --kube-proxy-config kube-proxy.json
+    az aks update --resource-group <resourceGroup> --name <clusterName> --kube-proxy-config kube-proxy.json
     ```
 
 ## Next steps

articles/aks/create-nginx-ingress-private-controller.md

@@ -52,7 +52,7 @@ az network vnet create \
 You create a DNS zone using the [az network private-dns zone create][az-network-private-dns-zone-create] command, specifying the name of the zone and the resource group to create it in. The following example creates a DNS zone named *private.contoso.com* in the *myResourceGroup* resource group.
 
 ```azurecli-interactive
-az network private-dns zone create --resource-group myResourceGoup -n private.contoso.com
+az network private-dns zone create --resource-group myResourceGoup --name private.contoso.com
 ```
 
 You create a virtual network link to the DNS zone created earlier using the [az network private-dns link vnet create][az-network-private-dns-link-vnet-create] command. The following example creates a link named *myDNSLink* to the zone *private.contoso.com* for the virtual network *myAzureVNet*. Include the `--registration-enabled` parameter to specify the link is not registration enabled.

articles/aks/csi-storage-drivers.md

@@ -50,7 +50,7 @@ To enable CSI storage drivers on a new cluster, include one of the following par
 * `--enable-snapshot-controller` allows you to enable the [snapshot controller][snapshot-controller].
 
 ```azurecli
-az aks update -n myAKSCluster -g myResourceGroup --enable-disk-driver --enable-file-driver --enable-blob-driver --enable-snapshot-controller
+az aks update --name myAKSCluster --resource-group myResourceGroup --enable-disk-driver --enable-file-driver --enable-blob-driver --enable-snapshot-controller
 ```
 
 It may take several minutes to complete this action. Once it's complete, you should see in the output the status of enabling the driver on your cluster. The following example resembles the section indicating the results when enabling the Blob storage CSI driver:
@@ -72,13 +72,13 @@ To disable CSI storage drivers on a new cluster, include one of the following pa
 * `--disable-snapshot-controller` allows you to disable the [snapshot controller][snapshot-controller].
 
 ```azurecli
-az aks create -n myAKSCluster -g myResourceGroup --disable-disk-driver --disable-file-driver --disable-blob-driver --disable-snapshot-controller 
+az aks create --name myAKSCluster --resource-group myResourceGroup --disable-disk-driver --disable-file-driver --disable-blob-driver --disable-snapshot-controller 
 ```
 
 To disable CSI storage drivers on an existing cluster, use one of the parameters listed earlier depending on the storage system:
 
 ```azurecli
-az aks update -n myAKSCluster -g myResourceGroup --disable-disk-driver --disable-file-driver --disable-blob-driver --disable-snapshot-controller 
+az aks update --name myAKSCluster --resource-group myResourceGroup --disable-disk-driver --disable-file-driver --disable-blob-driver --disable-snapshot-controller 
 ```
 
 ## Migrate custom in-tree storage classes to CSI