fix(argo-workflows): Restore RBAC permission and clarify namespace settings. (#989)

Signed-off-by: Vlad Losev <vladimir.losev@sage.com>
This commit is contained in:
Vlad Losev 2021-11-01 21:12:45 +03:00 committed by GitHub
parent 6fe7f57fb2
commit c1e7213cdc
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
7 changed files with 19 additions and 23 deletions

View file

@ -19,12 +19,14 @@ fullnameOverride:
##
kubeVersionOverride: ""
# Restrict Argo to only deploy into a single namespace by apply Roles and RoleBindings instead of the Cluster equivalents,
# and start argo-cli with the --namespaced flag. Use it in clusters with strict access policy.
# Restrict Argo to operate only in a single namespace (the namespace of the
# Helm release) by apply Roles and RoleBindings instead of the Cluster
# equivalents, and start workflow-controller with the --namespaced flag. Use it
# in clusters with strict access policy.
singleNamespace: false
workflow:
namespace: # Deprecated, for backwards compatibility: specify a single namespace to run workflows in
namespace: # Deprecated; use controller.workflowNamespaces instead.
serviceAccount:
create: false # Specifies whether a service account should be created
annotations: {}
@ -111,8 +113,9 @@ controller:
# Annotations applied to created service account
annotations: {}
name: workflow-controller
# Specify all namespaces to run worksflows need to be able to run in. This controls where the service
# account and RBAC resources will be created. If unspecified, will run in the default namespace.
# Specify all namespaces where this workflow controller instance will manage
# workflows. This controls where the service account and RBAC resources will
# be created. Only valid when singleNamespace is false.
workflowNamespaces:
- default
containerRuntimeExecutor: docker