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.
This commit is contained in:
Ruben Hensen committed 2026-10-23 17:44:08 +02:00
1 parent 69a0661d09
commit 134774509d
6 files changed
+67 -8

No files matched your search

+2
View File
@@ -8,6 +8,7 @@ namespace: argocd
resources:
- https://raw.githubusercontent.com/argoproj/argo-cd/refs/tags/v3.4.12/manifests/install.yaml
- ingress.yaml
- httproute.yaml
- oidc-secret.yaml
patches:
@@ -19,4 +20,5 @@ patches:
path: overlays/argocd-notifications-controller-patch.yaml
- path: overlays/argocd-cm.patch.yaml
- path: overlays/argocd-rbac-cm.patch.yaml
- path: overlays/argocd-cmd-params-cm.patch.yaml
- path: overlays/patched-ca-bundle.patch.yaml