From 7b4cc75138c2e8be0e47e9fe89978ca7f1d650c6 Mon Sep 17 00:00:00 2001 From: Max Gautier Date: Sat, 9 Nov 2024 14:12:10 +0100 Subject: [PATCH] Explain how to use dedicated node groups with labels and taints --- docs/_sidebar.md | 2 ++ .../dedicated_node_groups.md | 20 +++++++++++++++++++ 2 files changed, 22 insertions(+) create mode 100644 docs/manage_your_inventory/dedicated_node_groups.md diff --git a/docs/_sidebar.md b/docs/_sidebar.md index d30ec2a37..ad4c687b1 100644 --- a/docs/_sidebar.md +++ b/docs/_sidebar.md @@ -64,6 +64,8 @@ * [Ingress Nginx](/docs/ingress/ingress_nginx.md) * [Kube-vip](/docs/ingress/kube-vip.md) * [Metallb](/docs/ingress/metallb.md) +* Manage Your Inventory + * [Dedicated Node Groups](/docs/manage_your_inventory/dedicated_node_groups.md) * Operating Systems * [Amazonlinux](/docs/operating_systems/amazonlinux.md) * [Bootstrap-os](/docs/operating_systems/bootstrap-os.md) diff --git a/docs/manage_your_inventory/dedicated_node_groups.md b/docs/manage_your_inventory/dedicated_node_groups.md new file mode 100644 index 000000000..013b5171a --- /dev/null +++ b/docs/manage_your_inventory/dedicated_node_groups.md @@ -0,0 +1,20 @@ +# Dedicated node groups + +To reserved some nodes for particular workload (for instances, reserved GPU node for workload using them), you should +define an Ansible group for theses nodes (statically or dynamically) and set taints and labels for these those in your inventory, +using [Ansible group variable](https://docs.ansible.com/ansible/latest/inventory_guide/intro_inventory.html#assigning-a-variable-to-many-machines-group-variables). + +See below for concrete examples. + +## Nvidia GPU + +When using the Nvidia GPU support in kubespray, the nodes should have the following variables set: + +```yaml +node_taints: +- key: nvidia.com/gpu + effect: NoSchedule + ... (any other node taints) +``` + +TODO: add the same for labels once