Skip to content

Commit 320f2a9

Browse files
committed
formatting tweaks
1 parent c989ddf commit 320f2a9

7 files changed

+27
-27
lines changed

articles/aks/deploy-confidential-containers-default-policy.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -176,7 +176,7 @@ To configure the workload identity, perform the following steps described in the
176176
* Establish federated identity credential
177177
178178
>[!IMPORTANT]
179-
>For the step to **Export environmental variables**, set the value for the variable `SERVICE_ACCOUNT_NAMESPACE` to `kafka`.
179+
>For the step to **Export environment variables**, set the value for the variable `SERVICE_ACCOUNT_NAMESPACE` to `kafka`.
180180
181181
## Deploy a trusted application with kata-cc and attestation container
182182

articles/aks/learn/tutorial-kubernetes-workload-identity.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -56,9 +56,9 @@ The following example creates a resource group named *myResourceGroup* in the *e
5656
}
5757
```
5858
59-
## Export environmental variables
59+
## Export environment variables
6060
61-
To help simplify steps to configure the identities required, the steps below define environmental variables for reference on the cluster.
61+
To help simplify steps to configure the identities required, the steps below define environment variables for reference on the cluster.
6262
6363
* Create these variables using the following commands. Replace the default values for `RESOURCE_GROUP`, `LOCATION`, `SERVICE_ACCOUNT_NAME`, `SUBSCRIPTION`, `USER_ASSIGNED_IDENTITY_NAME`, and `FEDERATED_IDENTITY_CREDENTIAL_NAME`.
6464

articles/aks/quickstart-dapr.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -213,15 +213,15 @@ Now that both the Node.js and Python applications are deployed, you watch messag
213213
214214
### [Azure CLI](#tab/azure-cli)
215215
216-
* Remove the resource group, cluster, namespace, and all related resources using the [`az group delete`][az-group-delete] command.
216+
* Remove the resource group, cluster, namespace, and all related resources using the [az group delete][az-group-delete] command.
217217
218218
```azurecli-interactive
219219
az group delete --name MyResourceGroup
220220
```
221221
222222
### [Azure PowerShell](#tab/azure-powershell)
223223
224-
* Remove the resource group, cluster, namespace, and all related resources using the [`Remove-AzResourceGroup`][remove-azresourcegroup] command.
224+
* Remove the resource group, cluster, namespace, and all related resources using the [Remove-AzResourceGroup][remove-azresourcegroup] command.
225225
226226
```azurepowershell-interactive
227227
Remove-AzResourceGroup -Name MyResourceGroup

articles/aks/quickstart-event-grid.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@ In this quickstart, you create an AKS cluster and subscribe to AKS events.
2424

2525
### [Azure CLI](#tab/azure-cli)
2626

27-
Create an AKS cluster using the [`az aks create`][az-aks-create] command. The following example creates a resource group *MyResourceGroup* and a cluster named *MyAKS* with one node in the *MyResourceGroup* resource group:
27+
Create an AKS cluster using the [az aks create][az-aks-create] command. The following example creates a resource group *MyResourceGroup* and a cluster named *MyAKS* with one node in the *MyResourceGroup* resource group:
2828

2929
```azurecli-interactive
3030
az group create --name MyResourceGroup --location eastus
@@ -33,7 +33,7 @@ az aks create -g MyResourceGroup -n MyAKS --location eastus --node-count 1 --ge
3333

3434
### [Azure PowerShell](#tab/azure-powershell)
3535

36-
Create an AKS cluster using the [`New-AzAksCluster`][new-azakscluster] command. The following example creates a resource group *MyResourceGroup* and a cluster named *MyAKS* with one node in the *MyResourceGroup* resource group:
36+
Create an AKS cluster using the [New-AzAksCluster][new-azakscluster] command. The following example creates a resource group *MyResourceGroup* and a cluster named *MyAKS* with one node in the *MyResourceGroup* resource group:
3737

3838
```azurepowershell-interactive
3939
New-AzResourceGroup -Name MyResourceGroup -Location eastus
@@ -46,7 +46,7 @@ New-AzAksCluster -ResourceGroupName MyResourceGroup -Name MyAKS -Location eastus
4646

4747
### [Azure CLI](#tab/azure-cli)
4848

49-
Create a namespace and event hub using [`az eventhubs namespace create`][az-eventhubs-namespace-create] and [`az eventhubs eventhub create`][az-eventhubs-eventhub-create]. The following example creates a namespace *MyNamespace* and an event hub *MyEventGridHub* in *MyNamespace*, both in the *MyResourceGroup* resource group.
49+
Create a namespace and event hub using [az eventhubs namespace create][az-eventhubs-namespace-create] and [az eventhubs eventhub create][az-eventhubs-eventhub-create]. The following example creates a namespace *MyNamespace* and an event hub *MyEventGridHub* in *MyNamespace*, both in the *MyResourceGroup* resource group.
5050

5151
```azurecli-interactive
5252
az eventhubs namespace create --location eastus --name MyNamespace -g MyResourceGroup
@@ -56,7 +56,7 @@ az eventhubs eventhub create --name MyEventGridHub --namespace-name MyNamespace
5656
> [!NOTE]
5757
> The *name* of your namespace must be unique.
5858
59-
Subscribe to the AKS events using [`az eventgrid event-subscription create`][az-eventgrid-event-subscription-create]:
59+
Subscribe to the AKS events using [az eventgrid event-subscription create][az-eventgrid-event-subscription-create]:
6060

6161
```azurecli-interactive
6262
SOURCE_RESOURCE_ID=$(az aks show -g MyResourceGroup -n MyAKS --query id --output tsv)
@@ -181,7 +181,7 @@ az group delete --name MyResourceGroup --yes --no-wait
181181

182182
### [Azure PowerShell](#tab/azure-powershell)
183183

184-
Use the [`Remove-AzResourceGroup`][remove-azresourcegroup] cmdlet to remove the resource group, the AKS cluster, namespace, and event hub, and all related resources.
184+
Use the [Remove-AzResourceGroup][remove-azresourcegroup] cmdlet to remove the resource group, the AKS cluster, namespace, and event hub, and all related resources.
185185

186186
```azurepowershell-interactive
187187
Remove-AzResourceGroup -Name MyResourceGroup

articles/aks/quickstart-helm.md

Lines changed: 14 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Develop on Azure Kubernetes Service (AKS) with Helm
33
description: Use Helm with AKS and Azure Container Registry to package and run application containers in a cluster.
44
ms.topic: article
55
ms.custom: devx-track-azurecli, devx-track-azurepowershell
6-
ms.date: 12/26/2023
6+
ms.date: 01/18/2024
77
---
88

99
# Quickstart: Develop on Azure Kubernetes Service (AKS) with Helm
@@ -24,13 +24,13 @@ You need to store your container images in an Azure Container Registry (ACR) to
2424

2525
### [Azure CLI](#tab/azure-cli)
2626

27-
1. Create an Azure resource group using the [`az group create`][az-group-create] command. The following example creates a resource group named *myResourceGroup* in the *eastus* location.
27+
1. Create an Azure resource group using the [az group create](/cli/azure/group#az-group-create) command. The following example creates a resource group named *myResourceGroup* in the *eastus* location.
2828

2929
```azurecli-interactive
3030
az group create --name myResourceGroup --location eastus
3131
```
3232
33-
2. Create an Azure Container Registry using the [`az acr create`][az-acr-create] command. The following example creates an ACR named *myhelmacr* with the *Basic* SKU.
33+
2. Create an Azure Container Registry using the [az acr create][az-acr-create] command. The following example creates an ACR named *myhelmacr* with the *Basic* SKU.
3434
3535
```azurecli-interactive
3636
az acr create --resource-group myResourceGroup --name myhelmacr --sku Basic
@@ -62,13 +62,13 @@ You need to store your container images in an Azure Container Registry (ACR) to
6262
6363
### [Azure PowerShell](#tab/azure-powershell)
6464
65-
1. Create an Azure resource group using the [`New-AzResourceGroup`][new-azresourcegroup] cmdlet. The following example creates a resource group named *myResourceGroup* in the *eastus* location.
65+
1. Create an Azure resource group using the [New-AzResourceGroup][new-azresourcegroup] cmdlet. The following example creates a resource group named *myResourceGroup* in the *eastus* location.
6666
6767
```azurepowershell-interactive
6868
New-AzResourceGroup -Name myResourceGroup -Location eastus
6969
```
7070
71-
2. Create an Azure Container Registry using the [`New-AzContainerRegistry`][new-azcontainerregistry] cmdlet. The following example creates an ACR named *myhelmacr* with the *Basic* SKU.
71+
2. Create an Azure Container Registry using the [New-AzContainerRegistry][new-azcontainerregistry] cmdlet. The following example creates an ACR named *myhelmacr* with the *Basic* SKU.
7272
7373
```azurepowershell-interactive
7474
New-AzContainerRegistry -ResourceGroupName myResourceGroup -Name myhelmacr -Sku Basic
@@ -91,15 +91,15 @@ Your new AKS cluster needs access to your ACR to pull the container images and r
9191
9292
### [Azure CLI](#tab/azure-cli)
9393
94-
* Create an AKS cluster using the [`az aks create`][az-aks-create] command with the `--attach-acr` parameter to grant the cluster access to your ACR. The following example creates an AKS cluster named *myAKSCluster* and grants it access to the *myhelmacr* ACR. Make sure you replace `myhelmacr` with the name of your ACR.
94+
* Create an AKS cluster using the [az aks create][az-aks-create] command with the `--attach-acr` parameter to grant the cluster access to your ACR. The following example creates an AKS cluster named *myAKSCluster* and grants it access to the *myhelmacr* ACR. Make sure you replace `myhelmacr` with the name of your ACR.
9595
9696
```azurecli-interactive
9797
az aks create --resource-group myResourceGroup --name myAKSCluster --location eastus --attach-acr myhelmacr --generate-ssh-keys
9898
```
9999
100100
### [Azure PowerShell](#tab/azure-powershell)
101101
102-
* Create an AKS cluster using the [`New-AzAksCluster`][new-azakscluster] cmdlet with the `-AcrNameToAttach` parameter to grant the cluster access to your ACR. The following example creates an AKS cluster named *myAKSCluster* and grants it access to the *myhelmacr* ACR. Make sure you replace `myhelmacr` with the name of your ACR.
102+
* Create an AKS cluster using the [New-AzAksCluster][new-azakscluster] cmdlet with the `-AcrNameToAttach` parameter to grant the cluster access to your ACR. The following example creates an AKS cluster named *myAKSCluster* and grants it access to the *myhelmacr* ACR. Make sure you replace `myhelmacr` with the name of your ACR.
103103
104104
```azurepowershell-interactive
105105
New-AzAksCluster -ResourceGroupName myResourceGroup -Name myAKSCluster -Location eastus -AcrNameToAttach myhelmacr -GenerateSshKey
@@ -113,27 +113,27 @@ To connect a Kubernetes cluster locally, you use the Kubernetes command-line cli
113113
114114
### [Azure CLI](#tab/azure-cli)
115115
116-
1. Install `kubectl` locally using the [`az aks install-cli`][az-aks-install-cli] command.
116+
1. Install `kubectl` locally using the [az aks install-cli][az-aks-install-cli] command.
117117
118118
```azurecli-interactive
119119
az aks install-cli
120120
```
121121
122-
2. Configure `kubectl` to connect to your Kubernetes cluster using the [`az aks get-credentials`][az-aks-get-credentials] command. The following command gets credentials for the AKS cluster named *myAKSCluster* in *myResourceGroup*.
122+
2. Configure `kubectl` to connect to your Kubernetes cluster using the [az aks get-credentials][az-aks-get-credentials] command. The following command gets credentials for the AKS cluster named *myAKSCluster* in *myResourceGroup*.
123123
124124
```azurecli-interactive
125125
az aks get-credentials --resource-group myResourceGroup --name myAKSCluster
126126
```
127127
128128
### [Azure PowerShell](#tab/azure-powershell)
129129
130-
1. Install `kubectl` locally using the [`Install-AzAksKubectl`][install-azakskubectl] cmdlet.
130+
1. Install `kubectl` locally using the [Install-AzAksKubectl][install-azakskubectl] cmdlet.
131131
132132
```azurepowershell-interactive
133133
Install-AzAksKubectl
134134
```
135135
136-
2. Configure `kubectl` to connect to your Kubernetes cluster using the [`Import-AzAksCredential`][import-azakscredential] cmdlet. The following command gets credentials for the AKS cluster named *myAKSCluster* in *myResourceGroup*:
136+
2. Configure `kubectl` to connect to your Kubernetes cluster using the [Import-AzAksCredential][import-azakscredential] cmdlet. The following command gets credentials for the AKS cluster named *myAKSCluster* in *myResourceGroup*:
137137
138138
```azurepowershell-interactive
139139
Import-AzAksCredential -ResourceGroupName myResourceGroup -Name myAKSCluster
@@ -159,7 +159,7 @@ This quickstart uses the [Azure Vote application][azure-vote-app].
159159
160160
## Build and push the sample application to ACR
161161
162-
* Build and push the image to your ACR using the [`az acr build`][az-acr-build] command. The following example builds an image named *azure-vote-front:v1* and pushes it to the *myhelmacr* ACR. Make sure you replace `myhelmacr` with the name of your ACR.
162+
* Build and push the image to your ACR using the [az acr build][az-acr-build] command. The following example builds an image named *azure-vote-front:v1* and pushes it to the *myhelmacr* ACR. Make sure you replace `myhelmacr` with the name of your ACR.
163163
164164
```azurecli-interactive
165165
az acr build --image azure-vote-front:v1 --registry myhelmacr --file Dockerfile .
@@ -281,15 +281,15 @@ This quickstart uses the [Azure Vote application][azure-vote-app].
281281
282282
### [Azure CLI](#tab/azure-cli)
283283
284-
* Remove your resource group, AKS cluster, Azure container registry, container images stored in the ACR, and all related resources using the [`az group delete`][az-group-delete] command with the `--yes` parameter to confirm deletion and the `--no-wait` parameter to return to the command prompt without waiting for the operation to complete.
284+
* Remove your resource group, AKS cluster, Azure container registry, container images stored in the ACR, and all related resources using the [az group delete][az-group-delete] command with the `--yes` parameter to confirm deletion and the `--no-wait` parameter to return to the command prompt without waiting for the operation to complete.
285285
286286
```azurecli-interactive
287287
az group delete --name myResourceGroup --yes --no-wait
288288
```
289289
290290
### [Azure PowerShell](#tab/azure-powershell)
291291
292-
* Remove your resource group, AKS cluster, Azure container registry, container images stored in the ACR, and all related resources using the [`Remove-AzResourceGroup`][remove-azresourcegroup] cmdlet with the `--yes` parameter to confirm deletion and the `--no-wait` parameter to return to the command prompt without waiting for the operation to complete.
292+
* Remove your resource group, AKS cluster, Azure container registry, container images stored in the ACR, and all related resources using the [Remove-AzResourceGroup][remove-azresourcegroup] cmdlet with the `--yes` parameter to confirm deletion and the `--no-wait` parameter to return to the command prompt without waiting for the operation to complete.
293293
294294
```azurepowershell-interactive
295295
Remove-AzResourceGroup -Name myResourceGroup

articles/aks/tutorial-kubernetes-scale.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -76,7 +76,7 @@ This tutorial requires Azure PowerShell version 5.9.0 or later. Run `Get-Install
7676

7777
## Autoscale pods
7878

79-
To use the horizontal pod autoscaler, All containers must have defined CPU requests and limits, and pads have specified requests. In the `aks-store-quickstart` deployment, the *front-end* container requests 1m CPU with a limit of 1000m CPU.
79+
To use the horizontal pod autoscaler, all containers must have defined CPU requests and limits, and pods must have specified requests. In the `aks-store-quickstart` deployment, the *front-end* container requests 1m CPU with a limit of 1000m CPU.
8080

8181
These resource requests and limits are defined for each container, as shown in the following condensed example YAML:
8282

articles/aks/workload-identity-deploy-cluster.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -23,10 +23,10 @@ This article assumes you have a basic understanding of Kubernetes concepts. For
2323

2424
- If you have multiple Azure subscriptions, select the appropriate subscription ID in which the resources should be billed using the [az account][az-account] command.
2525

26-
## Export environmental variables
26+
## Export environment variables
2727

2828
To help simplify steps to configure the identities required, the steps below define
29-
environmental variables for reference on the cluster.
29+
environment variables for reference on the cluster.
3030

3131
Run the following commands to create these variables. Replace the default values for `RESOURCE_GROUP`, `LOCATION`, `SERVICE_ACCOUNT_NAME`, `SUBSCRIPTION`, `USER_ASSIGNED_IDENTITY_NAME`, and `FEDERATED_IDENTITY_CREDENTIAL_NAME`.
3232

0 commit comments

Comments
 (0)