From 310072e3e6497c401679f4a88cd501845c4a3856 Mon Sep 17 00:00:00 2001 From: Ryan Maleki Date: Tue, 15 Feb 2022 14:45:28 -0800 Subject: [PATCH] add command to configure local kubectl after creating an EKS cluster --- website/content/en/preview/getting-started/_index.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/website/content/en/preview/getting-started/_index.md b/website/content/en/preview/getting-started/_index.md index 679c1a1c5304..62859f15e375 100644 --- a/website/content/en/preview/getting-started/_index.md +++ b/website/content/en/preview/getting-started/_index.md @@ -78,6 +78,11 @@ eksctl create cluster -f cluster.yaml export CLUSTER_ENDPOINT="$(aws eks describe-cluster --name ${CLUSTER_NAME} --query "cluster.endpoint" --output text)" ``` +You can add the details of the newly created EKS cluster to your local kubectl as a new context by running: +```bash +aws eks update-kubeconfig --region ${AWS_DEFAULT_REGION} --name ${CLUSTER_NAME} +``` + This guide uses a managed node group to host Karpenter. Karpenter itself can run anywhere, including on [self-managed node groups](https://docs.aws.amazon.com/eks/latest/userguide/worker.html), [managed node groups](https://docs.aws.amazon.com/eks/latest/userguide/managed-node-groups.html), or [AWS Fargate](https://aws.amazon.com/fargate/).