From 3edd85b5bcf9b0971022254bf609e03d9df3e1d1 Mon Sep 17 00:00:00 2001 From: Carlos Manzanedo Rueda Date: Fri, 1 Jul 2022 06:25:47 +0100 Subject: [PATCH] final changes --- content/karpenter/040_karpenter/automatic_node_provisioning.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/content/karpenter/040_karpenter/automatic_node_provisioning.md b/content/karpenter/040_karpenter/automatic_node_provisioning.md index 08ee5262..945b8a13 100644 --- a/content/karpenter/040_karpenter/automatic_node_provisioning.md +++ b/content/karpenter/040_karpenter/automatic_node_provisioning.md @@ -283,3 +283,5 @@ In this section we have learned: * Karpenter can scale-out from zero when applications have available working pods and scale-in to zero when there are no running jobs or pods. +* Provisioners can be setup to define governance and rules that define how nodes will be provisioned within a cluster partition. We can setup requirements such as `karpenter.sh/capacity-type` to allow on-demand and spot instances or use `karpenter.k8s.aws/instance-size` to filter smaller sizes. The full list of supported labels is available **[here](https://karpenter.sh/v0.13.1/tasks/scheduling/#selecting-nodes)** +