From 23a2ef3ca9d1f58b95eef62e9c9b376891c3da05 Mon Sep 17 00:00:00 2001
From: Chris Grimmett <chris@grimtech.net>
Date: Mon, 22 Apr 2024 18:54:43 +0000
Subject: [PATCH] switch to letsencrypt-prod

---
 charts/argodeps/templates/ingress.yaml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/charts/argodeps/templates/ingress.yaml b/charts/argodeps/templates/ingress.yaml
index 65b62a9..fdf6872 100644
--- a/charts/argodeps/templates/ingress.yaml
+++ b/charts/argodeps/templates/ingress.yaml
@@ -4,7 +4,7 @@ metadata:
   name: argocd-server-ingress
   namespace: argocd
   annotations:
-    cert-manager.io/cluster-issuer: "letsencrypt-staging"
+    cert-manager.io/cluster-issuer: "letsencrypt-prod"
     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.