Skip to content

update eks docs to include config for the cluster token #543

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
blkgrlcto wants to merge 1 commit into
base: main
Choose a base branch
from
+11 −0
Open

update eks docs to include config for the cluster token #543

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions src/content/docs/aws/services/eks.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -686,6 +686,17 @@ The default version is `1.35`.

Users can specify the desired version when creating an EKS cluster in LocalStack using the `EKS_K3S_IMAGE_TAG` configuration variable when starting LocalStack.

## Configuring the k3d Cluster Token

When LocalStack creates a k3d-backed EKS cluster, it starts the k3s server with an explicit cluster token. This token is used to authenticate agent nodes joining the cluster, ensuring consistent behavior across k3d versions and enabling dynamic node registration (for example, when using Karpenter).
Copy link
Copy Markdown
Contributor

@nik-localstack nik-localstack Apr 7, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's not mention Karpenter in our docs since we don't fully support this yet. Also version compatibility is not very relevant as a pro for this change.

Suggested change
When LocalStack creates a k3d-backed EKS cluster, it starts the k3s server with an explicit cluster token. This token is used to authenticate agent nodes joining the cluster, ensuring consistent behavior across k3d versions and enabling dynamic node registration (for example, when using Karpenter).
When LocalStack creates a k3d-backed EKS cluster, it starts the k3s server with an explicit cluster token. This token is used to authenticate agent nodes joining the cluster, enabling dynamic node registration.

By default, LocalStack uses localstack-k3d-cluster-token as the cluster token. You can override this value using the `EKS_K3D_CLUSTER_TOKEN` configuration variable:
Copy link
Copy Markdown
Contributor

@nik-localstack nik-localstack Apr 7, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
By default, LocalStack uses localstack-k3d-cluster-token as the cluster token. You can override this value using the `EKS_K3D_CLUSTER_TOKEN` configuration variable:
By default, LocalStack uses `localstack-k3d-cluster-token` as the cluster token. You can override this value using the `EKS_K3D_CLUSTER_TOKEN` configuration variable:


```bash
EKS_K3D_CLUSTER_TOKEN=my-custom-token localstack start
```

Any agent nodes added to the cluster — whether via k3d node create or k3s agent — will use the same token to authenticate with the k3s server.

## Resource Browser

The LocalStack Web Application provides a Resource Browser for managing EKS clusters.
Expand Down