📦️ Publish initial cluster & argocd configuration

README.md

@@ -1,3 +1,16 @@
-# Git - ForgeJo
+# System configuration
 
-Configuration of the ForgeJO (Gitea open source fork) through ArgoCD
+This repo contains the `yaml` files used to configure the complete infrastructure. 
+
+
+## system/cluster
+
+Contains global cluster configuration (cluster issuer for automatic certificates)
+
+> This was only applied manually at cluster creation
+
+## system/argocd
+
+Configuration for ArgoCD to be accessible throug it's HTTP port with traefik and the automatic certificat system
+
+> This was only applied manually at cluster creation

system/argocd/argocd-ingress.yaml

@@ -0,0 +1,26 @@
+# For the ingress that connects to the HTTP port of ArgoCD
+apiVersion: networking.k8s.io/v1
+kind: Ingress
+metadata:
+  name: argocd-server-ingress
+  namespace: argocd
+  annotations:
+    cert-manager.io/cluster-issuer: "letsencrypt-http"
+    traefik.ingress.kubernetes.io/router.tls: "true"
+spec:
+  ingressClassName: traefik
+  tls:
+  - hosts:
+    - argo.qcampos.fr
+    secretName: argocd-server-tls
+  rules:
+  - host: argo.qcampos.fr
+    http:
+      paths:
+      - path: /
+        pathType: Prefix
+        backend:
+          service:
+            name: argocd-server
+            port:
+              number: 80

system/argocd/argocd-traefik.yaml

@@ -0,0 +1,8 @@
+# For Traefik to accept to speak with ArgoCD self-signed certificate
+apiVersion: traefik.io/v1alpha1
+kind: ServersTransport
+metadata:
+  name: argocd-server-transport
+  namespace: argocd
+spec:
+  insecureSkipVerify: true

system/cluster/cluster-issuer.yaml

@@ -0,0 +1,14 @@
+apiVersion: cert-manager.io/v1
+kind: ClusterIssuer
+metadata:
+  name: letsencrypt-http
+spec:
+  acme:
+    email: quentin.campos@gmail.com # Ton email pour les alertes de fin de validité
+    server: https://acme-v02.api.letsencrypt.org/directory
+    privateKeySecretRef:
+      name: letsencrypt-http-issuer-key
+    solvers:
+    - http01:
+        ingress:
+          class: traefik