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

Introduction

Starting with Terraform Enterprise 202502-1, you can configure a secondary hostname for your deployment. Please see the official release documentation here

Deploying Terraform Enterprise on Kubernetes/OpenShift using the official helm chart as documented here and using the ability for secondary hostname configuration requires helm chart release version 1.6.4 

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

Add the following values to create the required secondary service (e.g., 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>

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.