Ruben Hensen 134774509d argocd: serve plain HTTP behind the ingress and the Gateway ...

With server.insecure, TLS ends at nginx or Envoy and argocd-server serves plain HTTP, which is how Argo CD documents the Gateway API setup. The nginx Ingress now talks HTTP to the http port; the ssl-passthrough annotation did nothing without the controller flag. argocd-folder diffs server-side for the new HTTPRoute.

2026-10-23 17:44:08 +02:00

..

argocd-cm.patch copy.yaml

Add traccar client ingress

2025-03-09 13:00:02 +01:00

argocd-cm.patch.yaml

argocd: keep label-based resource tracking explicitly

2026-10-22 23:13:11 +02:00

argocd-cmd-params-cm.patch.yaml

argocd: serve plain HTTP behind the ingress and the Gateway

2026-10-23 17:44:08 +02:00

argocd-notifications-controller-patch.yaml

Add overlay patches 17

2024-09-14 22:12:34 +02:00

argocd-rbac-cm.patch.yaml

Add OIDC to argocd

2026-04-06 18:44:32 +02:00

patched-ca-bundle.patch.yaml

ca-bundle: also serve argocd, authentik and actual-budget

2026-10-22 09:26:43 +02:00