Argocd: Prepare switch to explicit certificates

argocd/overlays/jern.me/certificate.yaml

@@ -0,0 +1,13 @@
+apiVersion: cert-manager.io/v1
+kind: Certificate
+metadata:
+  name: argocd-fi-cert
+spec:
+  dnsNames:
+  - argocd.jern.fi
+  issuerRef:
+    group: cert-manager.io
+    kind: ClusterIssuer
+    name: letsencrypt-staging
+  secretName: argocd-fi-cert
+  revisionHistoryLimit: 5

argocd/overlays/jern.me/ingress.yaml

@@ -4,8 +4,6 @@ kind: Ingress
 metadata:
   name: argocd-server-ingress
   annotations:
-    cert-manager.io/cluster-issuer: letsencrypt-prod
-    kubernetes.io/tls-acme: "true"
     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.

argocd/overlays/jern.me/kustomization.yaml

@@ -11,6 +11,7 @@ labels:
 resources:
 - ../../bases/upstream
 - ingress.yaml
+- certificate.yaml
 - namespace.yaml
 
 patches:

argocd/overlays/kind/certificate.yaml

@@ -0,0 +1,13 @@
+apiVersion: cert-manager.io/v1
+kind: Certificate
+metadata:
+  name: argocd-cert
+spec:
+  dnsNames:
+  - argocd.local
+  issuerRef:
+    group: cert-manager.io
+    kind: ClusterIssuer
+    name: selfsigner
+  secretName: argocd-secret
+  revisionHistoryLimit: 5

argocd/overlays/kind/ingress.yaml

@@ -5,7 +5,6 @@ metadata:
   name: argocd-server-ingress
   annotations:
     cert-manager.io/cluster-issuer: selfsigned
-    kubernetes.io/tls-acme: "true"
     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.

argocd/overlays/kind/kustomization.yaml

@@ -12,3 +12,4 @@ resources:
 - ../../bases/upstream
 - namespace.yaml
 - ingress.yaml
+- certificate.yaml