First Commit

argocd/application.yaml

@@ -0,0 +1,77 @@
+# Public Argo CD example. Adjust the destination namespace, revision and values
+# for your environment, then apply this file once (or manage it from an
+# app-of-apps). Files under argocd/ are examples and are not rendered by Helm.
+apiVersion: argoproj.io/v1alpha1
+kind: Application
+metadata:
+  name: redis-cluster
+  namespace: argocd
+  finalizers:
+    - resources-finalizer.argocd.argoproj.io
+spec:
+  project: default
+  source:
+    repoURL: https://git.mulas.me/corrado/redis-cluster.git
+    targetRevision: master
+    path: .
+    helm:
+      releaseName: redis
+      valuesObject:
+        cluster:
+          shards: 3
+          replicasPerShard: 1
+
+        # Production deployments should authenticate even when Redis is only
+        # reachable inside the cluster. This example lets the chart create the
+        # initial password Secret; see the ignore rule below.
+        auth:
+          enabled: true
+
+        persistence:
+          # Empty selects the cluster's default StorageClass.
+          storageClass: ""
+          # This is per Redis member. The chart imposes no maximum.
+          size: 10Gi
+
+        # Disabled by default because this creates one LoadBalancer per member
+        # plus one balanced bootstrap LoadBalancer.
+        externalAccess:
+          enabled: false
+
+        metrics:
+          serviceMonitor:
+            enabled: false
+
+        # RedisInsight automatically discovers the release's balanced
+        # bootstrap endpoint. No IP address is required.
+        redisInsight:
+          enabled: true
+          persistence:
+            storageClass: ""
+            size: 2Gi
+          ingress:
+            enabled: false
+
+  destination:
+    server: https://kubernetes.default.svc
+    namespace: redis
+
+  syncPolicy:
+    automated:
+      prune: true
+      selfHeal: true
+    syncOptions:
+      - CreateNamespace=true
+      - RespectIgnoreDifferences=true
+
+  # Argo CD renders Helm without API access, so Helm's lookup cannot recover a
+  # previously generated password during comparison. Ignore the generated
+  # Secret data to keep the first password stable. Prefer an existing Secret
+  # managed by SOPS, Sealed Secrets or External Secrets for serious GitOps use.
+  ignoreDifferences:
+    - group: ""
+      kind: Secret
+      name: redis-redis-cluster
+      namespace: redis
+      jsonPointers:
+        - /data/redis-password