chore: Update Argo Workflows references to v3.7

Author: aniketpatil

manifests/kustomize/third-party/argo/base/kustomization.yaml

@@ -2,7 +2,7 @@ apiVersion: kustomize.config.k8s.io/v1beta1
 kind: Kustomization
 
 resources:
-- https://github.com/argoproj/argo-workflows/manifests/base/workflow-controller?ref=v3.6.7
+- https://github.com/argoproj/argo-workflows/manifests/base/workflow-controller?ref=v3.7.0 # updated from v3.6.7
 
 patches:
 - path: workflow-controller-deployment-patch.yaml

manifests/kustomize/third-party/argo/base/workflow-controller-configmap-patch.yaml

@@ -4,9 +4,10 @@ metadata:
   name: workflow-controller-configmap
 data:
   # References:
-  # * https://github.com/argoproj/argo-workflows/blob/v3.6.7/config/config.go
-  # * https://github.com/argoproj/argo-workflows/blob/v3.6.7/docs/workflow-controller-configmap.md
-  # * https://github.com/argoproj/argo-workflows/blob/v3.6.7/docs/workflow-controller-configmap.yaml
+  # * https://github.com/argoproj/argo-workflows/blob/v3.7.0/config/config.go
+  # * https://github.com/argoproj/argo-workflows/blob/v3.7.0/docs/workflow-controller-configmap.md
+  # * https://github.com/argoproj/argo-workflows/blob/v3.7.0/docs/workflow-controller-configmap.yaml
+
 
   # In artifactRepository.s3.endpoint, $(kfp-namespace) is needed, because in multi-user mode, pipelines may run in other namespaces.
   artifactRepository: |

manifests/kustomize/third-party/argo/base/workflow-controller-deployment-patch.yaml

@@ -10,12 +10,12 @@ spec:
           type: RuntimeDefault
       containers:
         - name: workflow-controller
-          image: quay.io/argoproj/workflow-controller:v3.6.7
+          image: quay.io/argoproj/workflow-controller:v3.7.0 # updated from v3.6.7
           args:
             - --configmap
             - workflow-controller-configmap
             - --executor-image
-            - quay.io/argoproj/argoexec:v3.6.7
+            - quay.io/argoproj/argoexec:v3.7.0 # updated from v3.6.7
           securityContext:
             readOnlyRootFilesystem: true
             runAsNonRoot: true

manifests/kustomize/third-party/argo/installs/cluster/kustomization.yaml

@@ -1,12 +1,9 @@
 apiVersion: kustomize.config.k8s.io/v1beta1
 kind: Kustomization
 
-  # Note, we do not explicitly separate cluster-scoped resources for cluster installation,
-  # because people who deploy cluster-scoped resources should be the same as who deploys
-  # namespaced resources.
 resources:
-- https://github.com/argoproj/argo-workflows/manifests/base/crds?ref=v3.6.7
-- https://github.com/argoproj/argo-workflows/manifests/cluster-install/workflow-controller-rbac?ref=v3.6.7
+- https://github.com/argoproj/argo-workflows/manifests/base/crds?ref=v3.7.0
+- https://github.com/argoproj/argo-workflows/manifests/cluster-install/workflow-controller-rbac?ref=v3.7.0
 - ../../base
 
 patches:

manifests/kustomize/third-party/argo/installs/cluster/workflow-controller-rbac-patch.yaml

@@ -0,0 +1,24 @@
+apiVersion: rbac.authorization.k8s.io/v1
+kind: ClusterRole
+metadata:
+  name: argo-cluster-role
+rules:
+  - apiGroups: [""]
+    resources: ["namespaces"]
+    verbs: ["get","list","watch"]
+  - apiGroups: ["argoproj.io"]
+    resources: ["clusterworkflowtemplates","workflows","workflowtemplates"]
+    verbs: ["get","list","watch","create","update","patch","delete"]
+---
+apiVersion: rbac.authorization.k8s.io/v1
+kind: ClusterRoleBinding
+metadata:
+  name: argo-cluster-role-binding
+subjects:
+  - kind: ServiceAccount
+    name: argo
+    namespace: argo
+roleRef:
+  kind: ClusterRole
+  name: argo-cluster-role
+  apiGroup: rbac.authorization.k8s.io

manifests/kustomize/third-party/argo/installs/cluster/workflowtaskresults-rbac.yaml

@@ -0,0 +1,21 @@
+apiVersion: rbac.authorization.k8s.io/v1
+kind: ClusterRole
+metadata:
+  name: argo-workflowtaskresults-role
+rules:
+  - apiGroups: ["argoproj.io"]
+    resources: ["workflowtaskresults"]
+    verbs: ["create","get","list","watch","update","patch","delete"]
+---
+apiVersion: rbac.authorization.k8s.io/v1
+kind: ClusterRoleBinding
+metadata:
+  name: argo-workflowtaskresults-role-binding
+subjects:
+  - kind: ServiceAccount
+    name: default        # workflow pods जे service account वापरत आहेत
+    namespace: argo      # argo namespace मध्ये
+roleRef:
+  kind: ClusterRole
+  name: argo-workflowtaskresults-role
+  apiGroup: rbac.authorization.k8s.io

manifests/kustomize/third-party/argo/installs/namespace/cluster-scoped/kustomization.yaml

@@ -2,4 +2,4 @@ apiVersion: kustomize.config.k8s.io/v1beta1
 kind: Kustomization
 resources:
 # Minimal CRDs omit schema validation, recommended for production cluster.
-- https://github.com/argoproj/argo-workflows/manifests/base/crds/minimal?ref=v3.6.7
+- https://github.com/argoproj/argo-workflows/manifests/base/crds/minimal?ref=v3.7.0

manifests/kustomize/third-party/argo/installs/namespace/kustomization.yaml

@@ -1,14 +1,16 @@
 apiVersion: kustomize.config.k8s.io/v1beta1
 kind: Kustomization
 
+namespace: argo # This namespace must match the namespace in the parent kustomization.yaml.
+
 # This kustomization.yaml mirrors the upstream Argo Workflows namespace-install configuration with remote references.
 # The differences:
 # * this does not include argo server.
 # * this separates cluster-scoped resources to its own folder.
 
 resources:
 - ../../base
-- https://github.com/argoproj/argo-workflows/manifests/namespace-install/workflow-controller-rbac?ref=v3.6.7
+- https://github.com/argoproj/argo-workflows/manifests/namespace-install/workflow-controller-rbac?ref=v3.7.0
 patches:
 - path: workflow-controller-deployment-patch.json
   target: