CNE GCP Ready: Configuring Argo CD Domain and TLS
Configure a custom domain and TLS certificate for Argo CD to access the GitOps interface through a secure endpoint.
Prerequisites
Before configuring the Argo CD domain, ensure you have these items:
- A deployed CNE environment
- A registered domain (for example,
argocd.mydomain.com) - A valid TLS certificate
- The certificate stored in Google Secret Manager
Identify the Argo CD Gateway Address
The CNE bootstrap process provisions a gateway for Argo CD access.
Retrieve the gateway address:
kubectl get gateway \
--namespace argocd-system \
--no-headers | awk '{print $3}'
The command returns the external hostname or IP address used by the Argo CD gateway.
Configure DNS
Create a DNS record in your DNS provider pointing your Argo CD subdomain to the gateway address.
Example:
argocd.mydomain.com → 34.xxx.xxx.xxx
To verify the DNS record, run:
dig argocd.mydomain.com
Configure Hostname and TLS
-
Update the Terraform configuration in your GitOps repository:
gitops/resources/terraform.tfvars -
Add the Argo CD domain configuration:
argocd_domain_config = { hostname = "argocd.mydomain.com" tls_external_secret_name = "liferay/certificates/mydomain" }
The tls_external_secret_name value must reference the secret containing the TLS certificate.
Commit and Push the Changes
Commit and push the updated configuration to the GitOps repository:
git add gitops/resources/terraform.tfvars
git commit -m "Configure Argo CD domain and TLS"
git push
Argo CD synchronizes the configuration changes automatically.
Verify the Configuration
Open the configured Argo CD URL in your browser.
https://argocd.mydomain.com
If the configuration is correct, the Argo CD UI loads with the configured TLS certificate.