From e4a31d7533e7bb8c0747e678ec09ce7d8ebc0ff0 Mon Sep 17 00:00:00 2001
From: Ruben Hensen <ruben.hensen@protonmail.com>
Date: Mon, 9 Sep 2024 15:01:31 +0200
Subject: [PATCH] Change to ssl passthrough

---
 argocd/ingress.yaml | 9 +++++++--
 1 file changed, 7 insertions(+), 2 deletions(-)

diff --git a/argocd/ingress.yaml b/argocd/ingress.yaml
index 58f9718..1f74eb9 100644
--- a/argocd/ingress.yaml
+++ b/argocd/ingress.yaml
@@ -3,8 +3,13 @@ kind: Ingress
 metadata:
   name: argocd-server-ingress
   annotations:
-    nginx.ingress.kubernetes.io/rewrite-target: /
+    # 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"
   namespace: argocd
 spec:
   ingressClassName: nginx
@@ -18,7 +23,7 @@ spec:
           service:
             name: argocd-server
             port: 
-              name: http
+              name: https
             
   # TLS configuration for HTTPS
   tls: