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

+3 -8
View File
@@ -3,13 +3,9 @@ kind: Ingress
metadata:
name: argocd-server-ingress
annotations:
# nginx.ingress.kubernetes.io/rewrite-target: /
cert-manager.io/cluster-issuer: prod-cluster-issuer
nginx.ingress.kubernetes.io/ssl-passthrough: "true"
# If you encounter a redirect loop or are getting a 307 response code
# then you need to force the nginx ingress to connect to the backend using HTTPS.
#
nginx.ingress.kubernetes.io/backend-protocol: "HTTPS"
# argocd-server runs with server.insecure, see overlays/
nginx.ingress.kubernetes.io/backend-protocol: "HTTP"
namespace: argocd
spec:
ingressClassName: nginx
@@ -23,9 +19,8 @@ spec:
service:
name: argocd-server
port:
name: https
name: http
tls:
- secretName: letsencrypt-prod
hosts:
- argocd.rubenhensen.nl