How to deploy Terraform Enterprise with secondary hostname using the helm chart

Introduction

Starting with Terraform Enterprise version v202502-1, you can configure a secondary hostname for your deployment, as detailed in the official release notes. To use this feature when deploying with the official Terraform Enterprise Helm chart, you must use chart version 1.6.4 or newer.

Expected Outcome

Terraform Enterprise is deployed with a secondary hostname, configured via the Helm chart.

Prerequisites

• Terraform Enterprise release v202502-1 or newer.
• Terraform Enterprise Helm chart v1.6.4 or newer.

Procedure

1. Add the following values to your Helm configuration to create the required secondary service, such as a LoadBalancer. Ensure that the certificates are valid for the secondary hostname.

   serviceSecondary:
     annotations: null
     type: LoadBalancer
   tlsSecondary:
     certData: <base64_encoded_cert_pem>
     keyData: <base64_encoded_key_pem>

2. Set the following environment variables in your Helm configuration to specify the secondary hostname and direct services like OIDC, VCS, SAML, and Run Tasks to use it.

   env:
     variables:
       TFE_HOSTNAME_SECONDARY: "<your_secondary_fqdn>"
       TFE_OIDC_HOSTNAME_CHOICE: secondary
       TFE_VCS_HOSTNAME_CHOICE: secondary
       TFE_SAML_HOSTNAME_CHOICE: secondary
       TFE_RUN_TASK_HOSTNAME_CHOICE: secondary

Additional Information

• For more details, refer to the official documentation on configuring a secondary hostname for Terraform Enterprise.