From 7d2ebb4fd018ca15939bf0032eaa6861b9722c96 Mon Sep 17 00:00:00 2001 From: Jason Deal Date: Thu, 2 May 2024 14:01:48 -0700 Subject: [PATCH] some more doc updates --- website/content/en/preview/concepts/nodeclasses.md | 2 +- website/content/en/preview/tasks/managing-amis.md | 9 +++++++++ 2 files changed, 10 insertions(+), 1 deletion(-) diff --git a/website/content/en/preview/concepts/nodeclasses.md b/website/content/en/preview/concepts/nodeclasses.md index 30a206941bd6..f4c4553447ab 100644 --- a/website/content/en/preview/concepts/nodeclasses.md +++ b/website/content/en/preview/concepts/nodeclasses.md @@ -1226,7 +1226,7 @@ status: - arm64 ``` -However, specifying an `eksOptimized` term may allow Karpenter to discover more requirements. +However, specifying an `eksOptimized` term will allow Karpenter to discover additional requirement when available. For example, when using the AL2 EKS optimized family Karpenter will also discover accelerated AMIs and add the appropriate requirements. ```yaml spec: diff --git a/website/content/en/preview/tasks/managing-amis.md b/website/content/en/preview/tasks/managing-amis.md index 2d8e41c2df9b..8e2b9b5d01c5 100644 --- a/website/content/en/preview/tasks/managing-amis.md +++ b/website/content/en/preview/tasks/managing-amis.md @@ -112,6 +112,15 @@ amiSelectorTerms: - id: ami-052c9ea013e6e3567 ``` +Alternatively, AMIs can be discovered via tags. Once an AMI has been validated in a lower environment, it can be tagged for discovery by Karpenter. Karpenter will then begin using the new AMI without requiring an update to your `EC2NodeClasses`. + +```yaml +amiSelectorTerms: + - tags: + karpenter.sh/discovery: "${CLUSTER_NAME}" + environment: prod +``` + See the [**spec.amiSelectorTerms**]({{< relref "../concepts/nodeclasses/#specamiselectorterms" >}}) section of the NodeClasses page for details. Keep in mind, that this could prevent you from getting critical security patches when new AMIs are available, but it does give you control over exactly which AMI is running.