From db13430c372ffc66fda25c6cb13bbd095a6f7861 Mon Sep 17 00:00:00 2001 From: Chris Negus Date: Wed, 1 Nov 2023 19:11:09 -0400 Subject: [PATCH] Add cloudformation pointer to getting started (#4997) --- .../getting-started/getting-started-with-karpenter/_index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/content/en/preview/getting-started/getting-started-with-karpenter/_index.md b/website/content/en/preview/getting-started/getting-started-with-karpenter/_index.md index 479f1156e8fe..21322dfe6346 100644 --- a/website/content/en/preview/getting-started/getting-started-with-karpenter/_index.md +++ b/website/content/en/preview/getting-started/getting-started-with-karpenter/_index.md @@ -68,7 +68,7 @@ echo $KARPENTER_VERSION $K8S_VERSION $CLUSTER_NAME $AWS_DEFAULT_REGION $AWS_ACCO Create a basic cluster with `eksctl`. The following cluster configuration will: -* Use CloudFormation to set up the infrastructure needed by the EKS cluster. +* Use CloudFormation to set up the infrastructure needed by the EKS cluster. See [CloudFormation]({{< relref "../../reference/cloudformation/" >}}) for a complete description of what `cloudformation.yaml` does for Karpenter. * Create a Kubernetes service account and AWS IAM Role, and associate them using IRSA to let Karpenter launch instances. * Add the Karpenter node role to the aws-auth configmap to allow nodes to connect. * Use [AWS EKS managed node groups](https://docs.aws.amazon.com/eks/latest/userguide/managed-node-groups.html) for the kube-system and karpenter namespaces. Uncomment fargateProfiles settings (and comment out managedNodeGroups settings) to use Fargate for both namespaces instead.