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

+14
View File
@@ -198,3 +198,17 @@ spec:
selector:
matchLabels:
kubernetes.io/metadata.name: vault
- name: https-argocd
protocol: HTTPS
port: 443
hostname: argocd.rubenhensen.nl
tls:
certificateRefs:
- name: letsencrypt-prod
namespace: argocd
allowedRoutes:
namespaces:
from: Selector
selector:
matchLabels:
kubernetes.io/metadata.name: argocd