some more doc updates

aws · May 2, 2024 · 7d2ebb4 · 7d2ebb4
1 parent 9bf7327
commit 7d2ebb4
Show file tree

Hide file tree

Showing 2 changed files with 10 additions and 1 deletion.
diff --git 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
@@ -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.