Files
charts/.vib/argo-workflows/runtime-parameters.yaml
Bitnami Bot c6d0a8cbaa [bitnami/argo-workflows] Release 6.4.1 (#23399)
* [bitnami/argo-workflows] Release 6.4.1 updating components versions

Signed-off-by: Bitnami Containers <bitnami-bot@vmware.com>

* Update CRDs automatically

Signed-off-by: Bitnami Containers <bitnami-bot@vmware.com>

* [bitnami/argo-workflows] Add extraDeploy to runtime-parameters.yaml

Signed-off-by: Gonzalo Gomez Gracia <gonzalog@vmware.com>

---------

Signed-off-by: Bitnami Containers <bitnami-bot@vmware.com>
Signed-off-by: Gonzalo Gomez Gracia <gonzalog@vmware.com>
Co-authored-by: Gonzalo Gomez Gracia <gonzalog@vmware.com>
2024-02-21 09:29:03 +01:00

46 lines
942 B
YAML

rbac:
singleNamespace: false
createAggregateRoles: true
server:
enabled: true
rbac:
create: true
auth:
enabled: true
mode: server
clusterWorkflowTemplates:
enabled: true
enableEditing: true
secure: false
service:
ports:
http: 80
type: LoadBalancer
workflows:
rbac:
create: true
postgresql:
enabled: true
service:
ports:
postgresql: 5432
mysql:
enabled: false
# The service account running the workflows needs to have 'patch' privileges on pods for the given namespace
# In our tests, that combination is 'default/default'
extraDeploy:
- |
apiVersion: rbac.authorization.k8s.io/v1
kind: RoleBinding
metadata:
name: default-cluster-admin
namespace: default
roleRef:
apiGroup: rbac.authorization.k8s.io
kind: ClusterRole
name: cluster-admin
subjects:
- kind: ServiceAccount
name: default
namespace: default