From 6dba96728959e6eda3cafb35f48415de0773e948 Mon Sep 17 00:00:00 2001 From: Mark Milligan Date: Wed, 24 May 2023 09:31:02 -0500 Subject: [PATCH] chore(docs): AWS EKS load balancer setup steps --- docs/install/kubernetes.md | 14 +++++++++++++- 1 file changed, 13 insertions(+), 1 deletion(-) diff --git a/docs/install/kubernetes.md b/docs/install/kubernetes.md index d65542d6c0ebd..62b3846955fd9 100644 --- a/docs/install/kubernetes.md +++ b/docs/install/kubernetes.md @@ -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: @@ -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