be46446e0c
* Parameterize artifact configuration **What** - Add parameterization of artifact store configuration **Why** Enables configuration of artifact repo secrets or omitting for use with IAM credentials * Add workflow CRD definition to argo chart **Why** The workflow CRD must exist in order for argo to function * artifactRepository values follow tree structure * Deploy CRD as a pre-install hook **What** Using `lachlanevenson/k8s-kubectl`, which appears to be the most popular, off the shelf container with `kubectl` applied, run a job to apply the `workflow` crd. **Why** CRD is not, and cannot, be parameterized with release and so attempting to deploy as a regular template causes failures when installing subsequent releases.
31 lines
777 B
YAML
31 lines
777 B
YAML
imagesNamespace: argoproj
|
|
controllerImage: workflow-controller
|
|
uiImage: argoui
|
|
executorImage: argoexec
|
|
imagesTag: v2.0.0-alpha3
|
|
controllerName: workflow-controller
|
|
|
|
# Enables ability to SSH into pod using web UI
|
|
enableWebConsole: false
|
|
uiName: ui
|
|
uiServiceType: LoadBalancer
|
|
crdVersion: v1alpha1
|
|
|
|
# If set to true then chart set controller instance id to release name
|
|
useReleaseAsInstanceID: false
|
|
instanceID:
|
|
|
|
useDefaultArtifactRepo: false
|
|
useStaticCredentials: true
|
|
|
|
# If set to true then chart installs minio and generate according artifactRepository section in workflow controller config map
|
|
installMinio: true
|
|
minioBucketName: argo-artifacts
|
|
|
|
artifactRepository:
|
|
s3:
|
|
accessKeySecret:
|
|
key: accesskey
|
|
secretKeySecret:
|
|
key: secretkey
|
|
insecure: true
|