edb3e6b41a
helm has issues with conditional sub charts of a sub chart so I think it'd be better to have minio not be installed as part of the chart by default so if you want to leverage this chart as part of another chart you don't have to worry about unintended resources getting created on cluster.
44 lines
1 KiB
YAML
44 lines
1 KiB
YAML
images:
|
|
namespace: argoproj
|
|
controller: workflow-controller
|
|
ui: argoui
|
|
executor: argoexec
|
|
tag: v2.1.1
|
|
|
|
controller:
|
|
serviceAccount: argo
|
|
name: workflow-controller
|
|
workflowNamespaces:
|
|
- default
|
|
# If set to true then chart set controller instance id to release name
|
|
useReleaseAsInstanceID: true
|
|
instanceID:
|
|
|
|
ui:
|
|
name: ui
|
|
serviceType: LoadBalancer
|
|
serviceAccount: argo-ui
|
|
# Enables ability to SSH into pod using web UI
|
|
enableWebConsole: false
|
|
|
|
crdVersion: v1alpha1
|
|
|
|
useDefaultArtifactRepo: false
|
|
useStaticCredentials: true
|
|
|
|
# If set to true then chart installs minio and generate according artifactRepository section in workflow controller config map
|
|
minio:
|
|
# This is not used by the subchart, but makes sense to group here.
|
|
install: false
|
|
defaultBucket:
|
|
enabled: true
|
|
name: argo-artifacts
|
|
|
|
artifactRepository:
|
|
s3:
|
|
#default minio creds
|
|
accessKeySecret:
|
|
key: AKIAIOSFODNN7EXAMPLE
|
|
secretKeySecret:
|
|
key: wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY
|
|
insecure: true
|