Skip to content

Commit 88aa5a5

Browse files
author
Jill Grant
authored
Merge pull request #274593 from schaffererin/aks-node-init-taints
Node taints and node init taints content
2 parents c8a3dbf + 8478b68 commit 88aa5a5

File tree

3 files changed

+350
-45
lines changed

3 files changed

+350
-45
lines changed

articles/aks/TOC.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -352,6 +352,8 @@
352352
href: use-tags.md
353353
- name: Labels
354354
href: use-labels.md
355+
- name: Node taints
356+
href: use-node-taints.md
355357
- name: Security
356358
items:
357359
- name: Container security

articles/aks/manage-node-pools.md

Lines changed: 2 additions & 45 deletions
Original file line numberDiff line numberDiff line change
@@ -322,50 +322,7 @@ When creating a node pool, you can add taints, labels, or tags to it. When you a
322322
323323
### Set node pool taints
324324
325-
1. Create a node pool with a taint using the [`az aks nodepool add`][az-aks-nodepool-add] command. Specify the name *taintnp* and use the `--node-taints` parameter to specify *sku=gpu:NoSchedule* for the taint.
326-
327-
```azurecli-interactive
328-
az aks nodepool add \
329-
--resource-group myResourceGroup \
330-
--cluster-name myAKSCluster \
331-
--name taintnp \
332-
--node-count 1 \
333-
--node-taints sku=gpu:NoSchedule \
334-
--no-wait
335-
```
336-
337-
2. Check the status of the node pool using the [`az aks nodepool list`][az-aks-nodepool-list] command.
338-
339-
```azurecli-interactive
340-
az aks nodepool list -g myResourceGroup --cluster-name myAKSCluster
341-
```
342-
343-
The following example output shows that the *taintnp* node pool is *Creating* nodes with the specified *nodeTaints*:
344-
345-
```output
346-
[
347-
{
348-
...
349-
"count": 1,
350-
...
351-
"name": "taintnp",
352-
"orchestratorVersion": "1.15.7",
353-
...
354-
"provisioningState": "Creating",
355-
...
356-
"nodeTaints": [
357-
"sku=gpu:NoSchedule"
358-
],
359-
...
360-
},
361-
...
362-
]
363-
```
364-
365-
The taint information is visible in Kubernetes for handling scheduling rules for nodes. The Kubernetes scheduler can use taints and tolerations to restrict what workloads can run on nodes.
366-
367-
* A **taint** is applied to a node that indicates only specific pods can be scheduled on them.
368-
* A **toleration** is then applied to a pod that allows them to *tolerate* a node's taint.
325+
AKS supports two kinds of node taints: node taints and node initialization taints (preview). For more information, see [Use node taints in an Azure Kubernetes Service (AKS) cluster][use-node-taints].
369326
370327
For more information on how to use advanced Kubernetes scheduled features, see [Best practices for advanced scheduler features in AKS][taints-tolerations]
371328
@@ -583,4 +540,4 @@ When you use an Azure Resource Manager template to create and manage resources,
583540
[use-tags]: use-tags.md
584541
[az-extension-add]: /cli/azure/extension#az_extension_add
585542
[az-extension-update]: /cli/azure/extension#az_extension_update
586-
543+
[use-node-taints]: ./use-node-taints.md

0 commit comments

Comments
 (0)