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. |
||
|---|---|---|
| .. | ||
| 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.