How-to make use of an internal load balancer with Terraform Enterprise Flexible Deployment Options Kubernetes (AWS)

Introduction

By default the overrides.yamlfile used with the Helm chart creates a public load balancer. If you would like to have an internal load balancer with AWS you will need to add a few lines to the overrides.yaml file

Expected Outcome

Instead of a public load balancer you will have an internal load balancer for your Terraform Enterprise environment

Prerequisites

• Implementing Terraform Enterprise - FDO kubernetes as described here  
• This example is for use with AWS

Use Case

• Make sure you have 2 private subnets where the load balancer can be created. These private subnets need to have certain tags for the EKS to know these can be used for the load balancer. Please see the documentation details from AWS here

• Add the following to your overrides.yamlfile

service:
  annotations:
    service.beta.kubernetes.io/aws-load-balancer-scheme: "internal"
    service.beta.kubernetes.io/aws-load-balancer-internal: "true"
  type: LoadBalancer # ClusterIP
  port: 443
  nodePort: 32443

• After installing the helm chart as documented here you should have an internal load balancer

NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
terraform-enterprise LoadBalancer 172.20.222.85 internal-a3917a5474b594204af56ceb8075b7d2-1835929486.eu-north-1.elb.amazonaws.com 443:32390/TCP 2m5s

Additional Information

• Application load balancing on Amazon EKS can be found here

• The Terraform Helm Chart details can be found here