Ingress — ArgoCD

The tdp-argo chart does not expose a single Ingress template or TDPConfiguration.gateway-style flags in this documentation. HTTP/HTTPS exposure generally follows the upstream argo-cd chart, with parameters passed under the tdp-argo: prefix.

Public URL

Ensure that the URL used by users matches tdp-argo.configs.cm.url (e.g., https://<host>), which is required for Dex/LDAP and correct links in the UI.

Ingress via argo-cd values (illustrative)

Check the current keys in the values.yaml of tdp-argo / argo-cd; a common pattern from the upstream chart is:

tdp-argo:
  server:
    ingress:
      enabled: true
      ingressClassName: <ingress-class>
      hostname: <host>
      path: /
      pathType: Prefix
      tls: true

Annotations (cert-manager, SSL redirect, etc.) depend on your Ingress Controller; configure them according to the controller you use.

Alternatives

• LoadBalancer on the server Service, when supported.
• Port-forward for testing: kubectl port-forward to the Argo CD server Service in the release namespace.

Troubleshooting

Issue	Solution
SSO/LDAP with wrong URL	Adjust tdp-argo.configs.cm.url to the actual host
Ingress not created	Check server.ingress keys in the exact chart version and whether the template is enabled
TLS	Verify the TLS Secret and controller annotations