DevFW-CICD/argocd-helm
6
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
argocd-helm/charts/argo/values.yaml

32 lines
777 B
YAML
Raw Normal View History

Create agro helm chart
2018-01-02 16:45:35 -08:00
imagesNamespace: argoproj
controllerImage: workflow-controller
uiImage: argoui
Support using release name for workflow controller instance id
2018-01-05 11:11:40 -08:00
executorImage: argoexec
Bump argo chart version
2018-03-23 21:19:37 -07:00
imagesTag: v2.1.0-alpha1
Create agro helm chart
2018-01-02 16:45:35 -08:00
controllerName: workflow-controller
Parameterize artifact repository settings (#4) * 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.
2018-03-23 21:10:05 -07:00
Support using release name for workflow controller instance id
2018-01-05 11:11:40 -08:00
# Enables ability to SSH into pod using web UI
Create agro helm chart
2018-01-02 16:45:35 -08:00
enableWebConsole: false
uiName: ui
Parameterize artifact repository settings (#4) * 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.
2018-03-23 21:10:05 -07:00
uiServiceType: LoadBalancer
Create agro helm chart
2018-01-02 16:45:35 -08:00
crdVersion: v1alpha1
Parameterize artifact repository settings (#4) * 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.
2018-03-23 21:10:05 -07:00
Support using release name for workflow controller instance id
2018-01-05 11:11:40 -08:00
# If set to true then chart set controller instance id to release name
useReleaseAsInstanceID: false
Create agro helm chart
2018-01-02 16:45:35 -08:00
instanceID:
Parameterize artifact repository settings (#4) * 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.
2018-03-23 21:10:05 -07:00
useDefaultArtifactRepo: false
useStaticCredentials: true
Support using release name for workflow controller instance id
2018-01-05 11:11:40 -08:00
# If set to true then chart installs minio and generate according artifactRepository section in workflow controller config map
Create agro helm chart
2018-01-02 16:45:35 -08:00
installMinio: true
minioBucketName: argo-artifacts
Parameterize artifact repository settings (#4) * 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.
2018-03-23 21:10:05 -07:00
artifactRepository:
s3:
accessKeySecret:
key: accesskey
secretKeySecret:
key: secretkey
insecure: true
Reference in a new issue Copy permalink