Update argo-cd to reflect new 1.2.0 deployment (#101) (#102)

charts/argo-cd/values.yaml

@@ -3,27 +3,29 @@ applicationController:
   servicePort: 8082
   image:
     repository: argoproj/argocd
-    tag: v1.1.2
+    tag: v1.2.0
     pullPolicy: Always
   volumeMounts: []
   volumes: []
 
 server:
   containerPort: 8080
+  metricsPort: 8083
   servicePortHttp: 80
   servicePortHttps: 443
   serviceAnnotations: {}
   image:
     repository: argoproj/argocd
-    tag: v1.1.2
-    pullPolicy: Always
-  uiInitImage:
-    repository: argoproj/argocd-ui
-    tag: v1.1.2
+    tag: v1.2.0
     pullPolicy: Always
   extraArgs: []
   volumeMounts: []
+  # - name: ssh-known-hosts
+  #   mountPath: /app/config/ssh
   volumes: []
+  # - name: ssh-known-hosts
+  #   configMap:
+  #     name: argocd-ssh-known-hosts-cm
   annotations: {}
 
 repoServer:
@@ -31,7 +33,7 @@ repoServer:
   servicePort: 8081
   image:
     repository: argoproj/argocd
-    tag: v1.1.2
+    tag: v1.2.0
     pullPolicy: Always
   volumeMounts: []
   volumes: []
@@ -47,7 +49,7 @@ dexServer:
     pullPolicy: Always
   initImage:
     repository: argoproj/argocd
-    tag: v1.1.2
+    tag: v1.2.0
     pullPolicy: Always
   volumeMounts: []
   volumes: []
@@ -55,23 +57,18 @@ dexServer:
 # terminate tls at ArgoCD level
 ingress:
   enabled: false
-  annotations: {}
+  annotations:
+    {}
     # kubernetes.io/ingress.class: nginx
     # nginx.ingress.kubernetes.io/force-ssl-redirect: "true"
     # nginx.ingress.kubernetes.io/ssl-passthrough: "true"
   path: /
   hosts:
     - argocd.example.com
-
-# Standard Argo CD installation with cluster-admin access.
-# Set this true if you plan to use Argo CD to deploy applications in the same cluster that
-#     Argo CD runs in (i.e. kubernetes.svc.default).
-# Will still be able to deploy to external clusters with inputted credentials.
-
 clusterAdminAccess:
   enabled: true
-
 config:
+  createSecret: true
   helmRepositories:
     # - name: privateRepo
     #   url: http://chartmuseum.privatecloud.com
@@ -123,8 +120,6 @@ config:
     githubSecret:
     gitlabSecret:
     bitbucketSecret:
-  # resourceCustomizations can be used to create custom health checks for resources
-  # https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/health.md#way-1-define-a-custom-health-check-in-argocd-cm-configmap
   resourceCustomizations:
   #   certmanager.k8s.io/Certificate:
   #     health.lua: |
@@ -141,13 +136,13 @@ config:
     #     args: ["sample args"]
 
 rbac:
-#   # An RBAC policy .csv file containing additional policy and role definitions.
-#   # See https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/rbac.md on how to write RBAC policies.
-#   policy.csv: |
-#     # Give all members of "my-org:team-alpha" the ability to sync apps in "my-project"
-#     p, my-org:team-alpha, applications, sync, my-project/*, allow
-#     # Make all members of "my-org:team-beta" admins
-#     g, my-org:team-beta, role:admin
+  #   # An RBAC policy .csv file containing additional policy and role definitions.
+  #   # See https://github.com/argoproj/argo-cd/blob/master/docs/operator-manual/rbac.md on how to write RBAC policies.
+  #   policy.csv: |
+  #     # Give all members of "my-org:team-alpha" the ability to sync apps in "my-project"
+  #     p, my-org:team-alpha, applications, sync, my-project/*, allow
+  #     # Make all members of "my-org:team-beta" admins
+  #     g, my-org:team-beta, role:admin
   policyCsv: #|
   #   p, role:org-admin, applications, *, */*, allow
   #   p, role:org-admin, clusters, get, *, allow
@@ -156,9 +151,7 @@ rbac:
   #   p, role:org-admin, repositories, update, *, allow
   #   p, role:org-admin, repositories, delete, *, allow
   #   g, your-github-org:your-team, role:org-admin
-  # The default role Argo CD will fall back to, when authorizing API requests
   policyDefault: #role:readonly
-  # Scopes controls which OIDC scopes to examine during rbac enforcement (in addition to `sub` scope).
   scopes: #[groups]
 
 redis: