1fed7f37cf
* moved workflow CRD into helpers.tpl * added new values to values.yaml * added UI cluster role and binding * add workflow controller cluster role and binding * added ui service account creator * added workflow controller service account yaml * reformatted values.yaml to group similar items * tweaked files to reflect values.yaml changes * setup minio stuff to match subchart model * changes to reflect minio rework * added README to explain chart a bit * changes made to reflect minio values changes * changes to reflect minio values changes (again) * updating minio to latest version * move the crd definition into it's own tpl file |
||
|---|---|---|
| .. | ||
| charts | ||
| templates | ||
| .helmignore | ||
| Chart.yaml | ||
| README.md | ||
| requirements.lock | ||
| requirements.yaml | ||
| values.yaml | ||
Argo Chart
This chart is used to set up argo and it's needed dependencies through one command. This is used in conjunction with helm.
If you want your deployment of this helm chart to most closely match the argo CLI, you should deploy it in the kube-system namespace.
Values
The values.yaml contains items used to tweak a deployment of this chart.
Fields to note:
controller.useReleaseAsInstanceID: If set to true then chart set controller instance id to release name- Note: If this is set to false then
controller.instanceIdmust be set
- Note: If this is set to false then
controller.workflowNamespaces: This is a list of namespaces where workflows will be ranui.enableWebConsole: Enables ability to SSH into pod using web UIminio.install: If this is true, we'll install minio and build out the artifactRepository section in workflow controller config map.artifactRepository.s3.accessKeySecretandartifactRepository.s3.secretKeySecretThese by default have the minio default credentials in them.