mirror of
https://github.com/rubenhensen/k8scd.git
synced 2026-11-15 14:29:09 +01:00
Ruben Hensen
134774509d
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.
27 lines
632 B
YAML
27 lines
632 B
YAML
apiVersion: networking.k8s.io/v1
|
|
kind: Ingress
|
|
metadata:
|
|
name: argocd-server-ingress
|
|
annotations:
|
|
cert-manager.io/cluster-issuer: prod-cluster-issuer
|
|
# argocd-server runs with server.insecure, see overlays/
|
|
nginx.ingress.kubernetes.io/backend-protocol: "HTTP"
|
|
namespace: argocd
|
|
spec:
|
|
ingressClassName: nginx
|
|
rules:
|
|
- host: argocd.rubenhensen.nl
|
|
http:
|
|
paths:
|
|
- path: /
|
|
pathType: Prefix
|
|
backend:
|
|
service:
|
|
name: argocd-server
|
|
port:
|
|
name: http
|
|
tls:
|
|
- secretName: letsencrypt-prod
|
|
hosts:
|
|
- argocd.rubenhensen.nl
|