# Secrets with credentials to pull images from a private registry
pullSecrets:[]
# - name: argo-pull-secret
init:
# By default the installation will not set an explicit one, which will mean it uses `default` for the namespace the chart is
# being deployed to. In RBAC clusters, that will almost certainly fail. See the NOTES: section of the readme for more info.
serviceAccount:""
createAggregateRoles:true
# 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.
singleNamespace:false
workflow:
namespace:""# Specify namespace if workflows run in another namespace than argo. This controls where the service account and RBAC resources will be created.
serviceAccount:
create:false# Specifies whether a service account should be created
annotations:{}
name:"argo-workflow"# Service account which is used to run workflows
rbac:
create:false# adds Role and RoleBinding for the above specified service account to be able to run workflows
controller:
image:
registry:quay.io
repository:argoproj/workflow-controller
# Overrides the image tag whose default is the chart appVersion.
tag:""
# parallelism dictates how many workflows can be running at the same time
parallelism:
# podAnnotations is an optional map of annotations to be applied to the controller Pods
podAnnotations:{}
# Optional labels to add to the controller pods
podLabels:{}
# SecurityContext to set on the controller pods
podSecurityContext:{}
# podPortName: http
metricsConfig:
enabled:false
path:/metrics
port:9090
servicePort:8080
servicePortName:metrics
# the controller container's securityContext
securityContext:
readOnlyRootFilesystem:true
runAsNonRoot:true
allowPrivilegeEscalation:false
capabilities:
drop:
- ALL
persistence:{}
# connectionPool:
# maxIdleConns: 100
# maxOpenConns: 0
# # save the entire workflow into etcd and DB
# nodeStatusOffLoad: false
# # enable archiving of old workflows
# archive: false
# postgresql:
# host: localhost
# port: 5432
# database: postgres
# tableName: argo_workflows
# # the database secrets must be in the same namespace of the controller
# userNameSecret:
# name: argo-postgres-config
# key: username
# passwordSecret:
# name: argo-postgres-config
# key: password
workflowDefaults:{}# Only valid for 2.7+
# spec:
# ttlStrategy:
# secondsAfterCompletion: 84600
# workflowWorkers: 32
# podWorkers: 32
workflowRestrictions:{}# Only valid for 2.9+
# templateReferencing: Strict|Secure
telemetryConfig:
enabled:false
path:/telemetry
port:8081
servicePort:8081
servicePortName:telemetry
serviceMonitor:
enabled:false
additionalLabels:{}
serviceAccount:
create:true
name:argo
# Annotations applied to created service account
annotations:{}
name:workflow-controller
workflowNamespaces:
- default
containerRuntimeExecutor:docker
instanceID:
# `instanceID.enabled` configures the controller to filter workflow submissions
# to only those which have a matching instanceID attribute.
enabled:false
# NOTE: If `instanceID.enabled` is set to `true` then either `instanceID.userReleaseName`
# or `instanceID.explicitID` must be defined.
# useReleaseName: true
# explicitID: unique-argo-controller-identifier
logging:
level:info
globallevel:"0"
serviceType:ClusterIP
# Annotations to be applied to the controller Service
serviceAnnotations:{}
# Optional labels to add to the controller Service
serviceLabels:{}
# Source ranges to allow access to service from. Only applies to
# service type `LoadBalancer`
loadBalancerSourceRanges:[]
resources:{}
# The list of environment variable definitions to be added to the controller
# manages container verbatim.
extraEnv:[]
# Extra arguments to be added to the controller
extraArgs:[]
replicas:1
pdb:
enabled:false
# minAvailable: 1
# maxUnavailable: 1
## Node selectors and tolerations for server scheduling to nodes with taints
