Skip to content

docs: add AWS EKS load balancer setup steps #7665

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

Merged
merged 1 commit into from
May 24, 2023
Merged

docs: add AWS EKS load balancer setup steps #7665

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
14 changes: 13 additions & 1 deletion docs/install/kubernetes.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -112,7 +112,7 @@ to log in and manage templates.
> [values.yaml](https://github.com/coder/coder/blob/main/helm/values.yaml)
> file directly.

If you are deploying Coder on AWS EKS and service is set to LoadBalancer, the load balancer external IP will be stuck in a pending status unless sessionAffinity is set to None.
If you are deploying Coder on AWS EKS and service is set to `LoadBalancer`, AWS will default to the Classic load balancer. The load balancer external IP will be stuck in a pending status unless sessionAffinity is set to None.

```yaml
coder:
Expand All @@ -121,6 +121,18 @@ to log in and manage templates.
sessionAffinity: None
```

AWS however recommends a Network load balancer in lieu of the Classic load balancer. Use the following `values.yaml` settings to request a Network load balancer:

```yaml
coder:
service:
externalTrafficPolicy: Local
sessionAffinity: None
annotations: {
service.beta.kubernetes.io/aws-load-balancer-type: "nlb"
}
```

1. Run the following command to install the chart in your cluster.

```console
Expand Down