From ca17ba8daf5f8ac393a744e4dd2f09db2f4203a0 Mon Sep 17 00:00:00 2001
From: Patrick Spek <p.spek@tyil.nl>
Date: Wed, 27 Jul 2022 10:16:02 +0200
Subject: Add ingress for ArgoCD

---
 playbooks.d/k3s-master/share/argocd/ingress.yaml | 31 ++++++++++++++++++++++++
 1 file changed, 31 insertions(+)
 create mode 100644 playbooks.d/k3s-master/share/argocd/ingress.yaml

(limited to 'playbooks.d')

diff --git a/playbooks.d/k3s-master/share/argocd/ingress.yaml b/playbooks.d/k3s-master/share/argocd/ingress.yaml
new file mode 100644
index 0000000..d3553e7
--- /dev/null
+++ b/playbooks.d/k3s-master/share/argocd/ingress.yaml
@@ -0,0 +1,31 @@
+---
+apiVersion: networking.k8s.io/v1
+kind: Ingress
+metadata:
+  name: argocd-server-ingress
+  namespace: argocd
+  annotations:
+    cert-manager.io/cluster-issuer: letsencrypt-prod
+    kubernetes.io/ingress.class: nginx
+    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.
+    nginx.ingress.kubernetes.io/backend-protocol: "HTTPS"
+spec:
+  rules:
+  - host: argo.tyil.nl
+    http:
+      paths:
+      - path: /
+        pathType: Prefix
+        backend:
+          service:
+            name: argocd-server
+            port:
+              name: https
+  tls:
+  - hosts:
+    - argo.tyil.nl
+    secretName: argocd-secret # do not change, this is provided by Argo CD
+...
-- 
cgit v1.1