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

@@ -0,0 +1,11 @@
apiVersion: v1
kind: ConfigMap
metadata:
name: argocd-cmd-params-cm
labels:
app.kubernetes.io/name: argocd-cmd-params-cm
app.kubernetes.io/part-of: argocd
data:
# TLS ends at the ingress, so argocd-server serves plain HTTP. Needed for
# the Gateway API, which has no simple way to trust its self-signed cert.
server.insecure: "true"