Try out the Helm chart for ArgoCD

1 files changed, 0 insertions, 31 deletions

diff --git a/playbooks.d/k3s-master/share/argocd/ingress.yaml b/playbooks.d/k3s-master/share/argocd/ingress.yaml
deleted file mode 100644
index d3553e7..0000000
--- a/playbooks.d/k3s-master/share/argocd/ingress.yaml
+++ /dev/null
@@ -1,31 +0,0 @@
----
-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
-...