Skip to content

Commit ced5b68

Browse files
schaffererinschaffererin
committed
Updates
1 parent 1eefe98 commit ced5b68

File tree

5 files changed

+74
-97
lines changed

5 files changed

+74
-97
lines changed

‎articles/aks/TOC.yml

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -237,7 +237,6 @@
237237
- name: Deploy a cluster with a fully managed resource group
238238
href: node-resource-group-lockdown.md
239239
- name: Scale an AKS cluster
240-
- name: Manually scale nodes in an AKS cluster
241240
href: scale-cluster.md
242241
- name: Stop and start an AKS cluster
243242
href: start-stop-cluster.md

‎articles/aks/concepts-clusters-workloads.md

Lines changed: 5 additions & 21 deletions
Original file line numberDiff line numberDiff line change
@@ -1,30 +1,14 @@
11
---
2-
title: Azure Kubernetes Services (AKS) Core Basic Concepts
3-
description: Learn about the core components that make up workloads and clusters in Kubernetes and their counterparts on Azure Kubernetes Services (AKS).
2+
title: Azure Kubernetes Services (AKS) core concepts
3+
description: Learn about the core components that make up workloads and clusters in Azure Kubernetes Service (AKS).
44
ms.topic: conceptual
55
ms.custom: build-2023
6-
ms.date: 01/16/2024
6+
ms.date: 04/16/2024
77
---
88

9-
# Core Kubernetes concepts for Azure Kubernetes Service
9+
# Core Kubernetes concepts for Azure Kubernetes Service (aks)
1010

11-
Application development continues to move toward a container-based approach, increasing our need to orchestrate and manage resources. As the leading platform, Kubernetes provides reliable scheduling of fault-tolerant application workloads. Azure Kubernetes Service (AKS), a managed Kubernetes offering, further simplifies container-based application deployment and management.
12-
13-
This article introduces core concepts:
14-
15-
* Kubernetes infrastructure components:
16-
17-
* *control plane*
18-
* *nodes*
19-
* *node pools*
20-
21-
* Workload resources:
22-
23-
* *pods*
24-
* *deployments*
25-
* *sets*
26-
27-
* Group resources using *namespaces*.
11+
This article describes core concepts of Azure Kubernetes Service (AKS), a managed Kubernetes service that you can use to deploy and operate containerized applications at scale on Azure. It helps you learn about the infrastructure components of Kubernetes and obtain a deeper understanding of how Kubernetes works in AKS.
2812

2913
## What is Kubernetes?
3014

‎articles/aks/create-node-pools.md

Lines changed: 29 additions & 30 deletions
Original file line numberDiff line numberDiff line change
@@ -45,15 +45,15 @@ The following limitations apply when you create AKS clusters that support multip
4545
1. Create an Azure resource group using the [`az group create`][az-group-create] command.
4646

4747
```azurecli-interactive
48-
az group create --name myResourceGroup --location eastus
48+
az group create --name $RESOURCE_GROUP_NAME --location $LOCATION
4949
```
5050
5151
2. Create an AKS cluster with a single node pool using the [`az aks create`][az-aks-create] command.
5252
5353
```azurecli-interactive
5454
az aks create \
55-
--resource-group myResourceGroup \
56-
--name myAKSCluster \
55+
--resource-group $RESOURCE_GROUP_NAME \
56+
--name $CLUSTER_NAME \
5757
--vm-set-type VirtualMachineScaleSets \
5858
--node-count 2 \
5959
--generate-ssh-keys \
@@ -65,7 +65,7 @@ The following limitations apply when you create AKS clusters that support multip
6565
3. When the cluster is ready, get the cluster credentials using the [`az aks get-credentials`][az-aks-get-credentials] command.
6666
6767
```azurecli-interactive
68-
az aks get-credentials --resource-group myResourceGroup --name myAKSCluster
68+
az aks get-credentials --resource-group $RESOURCE_GROUP_NAME --name $CLUSTER_NAME
6969
```
7070
7171
## Add a node pool
@@ -76,16 +76,16 @@ The cluster created in the previous step has a single node pool. In this section
7676
7777
```azurecli-interactive
7878
az aks nodepool add \
79-
--resource-group myResourceGroup \
80-
--cluster-name myAKSCluster \
81-
--name mynodepool \
79+
--resource-group $RESOURCE_GROUP_NAME \
80+
--cluster-name $CLUSTER_NAME \
81+
--name $NODE_POOL_NAME \
8282
--node-count 3
8383
```
8484
8585
2. Check the status of your node pools using the [`az aks node pool list`][az-aks-nodepool-list] command and specify your resource group and cluster name.
8686
8787
```azurecli-interactive
88-
az aks nodepool list --resource-group myResourceGroup --cluster-name myAKSCluster
88+
az aks nodepool list --resource-group $RESOURCE_GROUP_NAME --cluster-name $CLUSTER_NAME
8989
```
9090
9191
The following example output shows *mynodepool* has been successfully created with three nodes. When the AKS cluster was created in the previous step, a default *nodepool1* was created with a node count of *2*.
@@ -130,9 +130,9 @@ The ARM64 processor provides low power compute for your Kubernetes workloads. To
130130
131131
```azurecli-interactive
132132
az aks nodepool add \
133-
--resource-group myResourceGroup \
134-
--cluster-name myAKSCluster \
135-
--name armpool \
133+
--resource-group $RESOURCE_GROUP_NAME \
134+
--cluster-name $CLUSTER_NAME \
135+
--name $ARM_NODE_POOL_NAME \
136136
--node-count 3 \
137137
--node-vm-size Standard_D2pds_v5
138138
```
@@ -147,9 +147,9 @@ The Azure Linux container host for AKS is an open-source Linux distribution avai
147147
148148
```azurecli-interactive
149149
az aks nodepool add \
150-
--resource-group myResourceGroup \
151-
--cluster-name myAKSCluster \
152-
--name azlinuxpool \
150+
--resource-group $RESOURCE_GROUP_NAME \
151+
--cluster-name $CLUSTER_NAME \
152+
--name $AZ_LINUX_NODE_POOL_NAME \
153153
--os-sku AzureLinux
154154
```
155155
@@ -182,11 +182,11 @@ A workload may require splitting cluster nodes into separate pools for logical i
182182
183183
```azurecli-interactive
184184
az aks nodepool add \
185-
--resource-group myResourceGroup \
186-
--cluster-name myAKSCluster \
187-
--name mynodepool \
185+
--resource-group $RESOURCE_GROUP_NAME \
186+
--cluster-name $CLUSTER_NAME \
187+
--name $NODE_POOL_NAME \
188188
--node-count 3 \
189-
--vnet-subnet-id <YOUR_SUBNET_RESOURCE_ID>
189+
--vnet-subnet-id $SUBNET_RESOURCE_ID
190190
```
191191
192192
## FIPS-enabled node pools
@@ -213,10 +213,10 @@ Beginning in Kubernetes version 1.20 and higher, you can specify `containerd` as
213213
214214
```azurecli-interactive
215215
az aks nodepool add \
216-
--resource-group myResourceGroup \
217-
--cluster-name myAKSCluster \
216+
--resource-group $RESOURCE_GROUP_NAME \
217+
--cluster-name $CLUSTER_NAME \
218218
--os-type Windows \
219-
--name npwcd \
219+
--name $CONTAINER_D_NODE_POOL_NAME \
220220
--node-vm-size Standard_D4s_v3 \
221221
--kubernetes-version 1.20.5 \
222222
--aks-custom-headers WindowsContainerRuntime=containerd \
@@ -229,9 +229,9 @@ Beginning in Kubernetes version 1.20 and higher, you can specify `containerd` as
229229
230230
```azurecli-interactive
231231
az aks nodepool upgrade \
232-
--resource-group myResourceGroup \
233-
--cluster-name myAKSCluster \
234-
--name npwd \
232+
--resource-group $RESOURCE_GROUP_NAME \
233+
--cluster-name $CLUSTER_NAME \
234+
--name $CONTAINER_D_NODE_POOL_NAME \
235235
--kubernetes-version 1.20.7 \
236236
--aks-custom-headers WindowsContainerRuntime=containerd
237237
```
@@ -242,8 +242,8 @@ Beginning in Kubernetes version 1.20 and higher, you can specify `containerd` as
242242
243243
```azurecli-interactive
244244
az aks nodepool upgrade \
245-
--resource-group myResourceGroup \
246-
--cluster-name myAKSCluster \
245+
--resource-group $RESOURCE_GROUP_NAME \
246+
--cluster-name $CLUSTER_NAME \
247247
--kubernetes-version 1.20.7 \
248248
--aks-custom-headers WindowsContainerRuntime=containerd
249249
```
@@ -259,11 +259,11 @@ Beginning in Kubernetes version 1.20 and higher, you can specify `containerd` as
259259
>
260260
261261
```azurecli-interactive
262-
az aks nodepool add --name ephemeral --cluster-name myAKSCluster --resource-group myResourceGroup -s Standard_DS3_v2 --node-osdisk-type Ephemeral
262+
az aks nodepool add --name $EPHEMERAL_NODE_POOL_NAME --cluster-name $CLUSTER_NAME --resource-group $RESOURCE_GROUP_NAME -s Standard_DS3_v2 --node-osdisk-type Ephemeral
263263
```
264264
265265
> [!IMPORTANT]
266-
> With Ephemeral OS, you can deploy VM and instance images up to the size of the VM cache. In the AKS case, the default node OS disk configuration uses 128 GB, which means that you need a VM size that has a cache larger than 128 GB. The default Standard_DS2_v2 has a cache size of 86 GB, which isn't large enough. The Standard_DS3_v2 has a cache size of 172 GB, which is large enough. You can also reduce the default size of the OS disk by using `--node-osdisk-size`. The minimum size for AKS images is 30 GB.
266+
> With Ephemeral OS, you can deploy VMs and instance images up to the size of the VM cache. The default node OS disk configuration in AKS uses 128 GB, which means that you need a VM size that has a cache larger than 128 GB. The default Standard_DS2_v2 has a cache size of 86 GB, which isn't large enough. The Standard_DS3_v2 VM SKU has a cache size of 172 GB, which is large enough. You can also reduce the default size of the OS disk by using `--node-osdisk-size`, but keep in mind the minimum size for AKS images is 30 GB.
267267
268268
## Delete a node pool
269269
@@ -275,7 +275,7 @@ If you no longer need a node pool, you can delete it and remove the underlying V
275275
* Delete a node pool using the [`az aks nodepool delete`][az-aks-nodepool-delete] command and specify the node pool name.
276276
277277
```azurecli-interactive
278-
az aks nodepool delete -g myResourceGroup --cluster-name myAKSCluster --name mynodepool --no-wait
278+
az aks nodepool delete --resource-group $RESOURCE_GROUP_NAME --cluster-name $CLUSTER_NAME --name $NODE_POOL_NAME --no-wait
279279
```
280280
281281
It takes a few minutes to delete the nodes and the node pool.
@@ -292,7 +292,6 @@ In this article, you learned how to create multiple node pools in an AKS cluster
292292
[az-aks-get-credentials]: /cli/azure/aks#az_aks_get_credentials
293293
[az-aks-create]: /cli/azure/aks#az_aks_create
294294
[az-aks-update]: /cli/azure/aks#az_aks_update
295-
[az-aks-delete]: /cli/azure/aks#az_aks_delete
296295
[az-aks-nodepool]: /cli/azure/aks/nodepool
297296
[az-aks-nodepool-add]: /cli/azure/aks/nodepool#az_aks_nodepool_add
298297
[az-aks-nodepool-list]: /cli/azure/aks/nodepool#az_aks_nodepool_list

‎articles/aks/generation-2-vm-windows.md

Lines changed: 20 additions & 25 deletions
Original file line numberDiff line numberDiff line change
@@ -10,28 +10,23 @@ author: schaffererin
1010

1111
# Use generation 2 virtual machines on Windows in Azure Kubernetes Service (AKS) (preview)
1212

13-
Azure supports [Generation 2 (Gen2) virtual machines (VMs)](../virtual-machines/generation-2.md). Gen 2 VMs support key features not supported in generation 1 (Gen1) VMs, including increased memory, Intel Software Guard Extensions (Intel SGX), and virtualized persistent memory (vPMEM).
13+
Azure supports [Generation 2 (Gen 2) virtual machines (VMs)](../virtual-machines/generation-2.md). Gen 2 VMs support key features not supported in Generation 1 (Gen 1) VMs, including increased memory, Intel Software Guard Extensions (Intel SGX), and virtualized persistent memory (vPMEM).
1414

15-
Gen 2 VMs use the new UEFI-based boot architecture rather than the BIOS-based architecture used by gen 1 VMs. Only specific SKUs and sizes support Gen2 VMs. Check the [list of supported sizes](../virtual-machines/generation-2.md#generation-2-vm-sizes) to see if your SKU supports or requires Gen2.
15+
Gen 2 VMs use the new UEFI-based boot architecture rather than the BIOS-based architecture used by Gen 1 VMs. Only specific SKUs and sizes support Gen 2 VMs. Check the [list of supported sizes](../virtual-machines/generation-2.md#generation-2-vm-sizes) to see if your SKU supports or requires Gen 2.
1616

17-
Additionally, not all VM images support Gen2 VMs. On AKS, Gen2 VMs use the AKS Ubuntu 22.04 or 18.04 image or the AKS Windows Server 2022 image. These images support all Gen2 SKUs and sizes.
17+
Additionally, not all VM images support Gen 2 VMs. On AKS, Gen 2 VMs use the AKS Ubuntu 22.04 or 18.04 image or the AKS Windows Server 2022 image. These images support all Gen 2 SKUs and sizes.
1818

1919
[!INCLUDE [preview features callout](includes/preview/preview-callout.md)]
2020

21-
## Considerations
22-
23-
* Generation 2 VMs are supported on Windows for WS2022 only.
24-
* Generation 2 VMs are default for Windows clusters greater than or equal to Kubernetes 1.25.
25-
* If your Kubernetes version is greater than 1.25, you only need to set the `vm_size` to get the generation 2 node pool. You can still use WS2019 generation 1 if you define that in the `os_sku`.
26-
* If your Kubernetes version is less than 1.25, you can set the `os_sku` to WS2022 and set the `vm_size` to generation 2 to get the generation 2 node pool.
27-
2821
## Before you begin
2922

3023
Before you begin, you need the following resources installed and configured:
3124

3225
* The Azure CLI version 2.44.0 or later. Run `az --version` to find the current version. If you need to install or upgrade, see [Install Azure CLI][azure-cli-install].
3326
* The `aks-preview` extension version 0.5.126 or later.
3427
* The `AKSWindows2022Gen2Preview` feature flag registered on your subscription.
28+
* Generation 2 VMs are supported on Windows for Windows Server 2022 (WS2022) only.
29+
* Generation 2 VMs are default for Windows clusters running Kubernetes 1.25 or later.
3530

3631
### Install the `aks-preview` Azure CLI extension
3732

@@ -67,49 +62,49 @@ Before you begin, you need the following resources installed and configured:
6762
az provider register --namespace "Microsoft.ContainerService"
6863
```
6964
70-
## Create a Windows node pool with a generation 2 VM
65+
## Create a Windows node pool with a Generation 2 VM
7166
72-
1. Create a Windows node pool with a generation 2 VM using the [`az aks nodepool add`][az-aks-nodepool-add] command.
67+
1. Check available Generation 2 VM sizes using the [`az vm list`][az-vm-list] command.
7368
7469
```azurecli-interactive
75-
az aks nodepool add --resource-group <resource-group-name> --cluster-name <cluster-name> --name <node-pool-name> --os-type Windows --os-sku Windows2022
70+
az vm list -skus --location <location> --size <vm-size> --output table
7671
```
7772
78-
2. Verify successful node pool creation using the [`az aks nodepool show`][az-aks-nodepool-show] command and check that the `nodeImageVersion` contains `gen2` in the output.
73+
2. Create a Windows node pool with a Generation 2 VM using the [`az aks nodepool add`][az-aks-nodepool-add] command.
7974
8075
```azurecli-interactive
81-
az aks nodepool show --resource-group <resource-group-name> --cluster-name <cluster-name> --name <node-pool-name>
76+
az aks nodepool add --resource-group <resource-group-name> --cluster-name <cluster-name> --name <node-pool-name> --os-type Windows --os-sku Windows2022
8277
```
8378
84-
3. Check available generation 2 VM sizes using the [`az vm list`][az-vm-list] command.
79+
3. Verify a successful node pool creation using the [`az aks nodepool show`][az-aks-nodepool-show] command and check that the `nodeImageVersion` contains `gen2` in the output.
8580
8681
```azurecli-interactive
87-
az vm list -skus --location <location> --size <vm-size> --output table
82+
az aks nodepool show --resource-group <resource-group-name> --cluster-name <cluster-name> --name <node-pool-name>
8883
```
8984
90-
## Update a Windows node pool to a generation 2 VM
85+
## Update a Windows node pool to a Generation 2 VM
9186
92-
1. Update a Windows node pool to a generation 2 VM using the [`az aks nodepool update`][az-aks-nodepool-update] command.
87+
1. Check available Generation 2 VM sizes using the [`az vm list`][az-vm-list] command.
9388
9489
```azurecli-interactive
95-
az aks nodepool update --resource-group <resource-group-name> --cluster-name <cluster-name> --name <node-pool-name> --os-type Windows --os-sku Windows2022
90+
az vm list -skus --location <location> --size <vm-size> --output table
9691
```
9792
98-
2. Verify successful node pool update using the [`az aks nodepool show`][az-aks-nodepool-show] command and check that the `nodeImageVersion` contains `gen2` in the output.
93+
2. Update a Windows node pool to a Generation 2 VM using the [`az aks nodepool update`][az-aks-nodepool-update] command.
9994
10095
```azurecli-interactive
101-
az aks nodepool show --resource-group <resource-group-name> --cluster-name <cluster-name> --name <node-pool-name>
96+
az aks nodepool update --resource-group <resource-group-name> --cluster-name <cluster-name> --name <node-pool-name> --os-type Windows --os-sku Windows2022
10297
```
10398
104-
3. Check available generation 2 VM sizes using the [`az vm list`][az-vm-list] command.
99+
3. Verify a successful node pool update using the [`az aks nodepool show`][az-aks-nodepool-show] command and check that the `nodeImageVersion` contains `gen2` in the output.
105100
106101
```azurecli-interactive
107-
az vm list -skus --location <location> --size <vm-size> --output table
102+
az aks nodepool show --resource-group <resource-group-name> --cluster-name <cluster-name> --name <node-pool-name>
108103
```
109104
110105
## Next steps
111106
112-
To learn more about generation 2 VMs, see [Support for generation 2 VMs on Azure](../virtual-machines/generation-2.md).
107+
To learn more about Generation 2 VMs, see [Support for Generation 2 VMs on Azure](../virtual-machines/generation-2.md).
113108
114109
<!-- LINKS -->
115110
[azure-cli-install]: /cli/azure/install-azure-cli

0 commit comments

Comments
 (0)