DevFW-CICD/argocd-helm
6
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
argocd-helm/charts/argo/templates/workflow-controller-config-map.yaml

49 lines
2.2 KiB
YAML
Raw Normal View History

Create agro helm chart
2018-01-02 16:45:35 -08:00
apiVersion: v1
kind: ConfigMap
metadata:
Updating helm chart and improving style (#7) * 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
2018-06-04 10:39:53 -04:00
name: {{ .Release.Name }}-{{ .Values.controller.name }}-configmap
Create agro helm chart
2018-01-02 16:45:35 -08:00
labels:
chart: {{ .Chart.Name }}-{{ .Chart.Version | replace "+" "_" }}
release: {{ .Release.Name }}
heritage: {{ .Release.Service }}
data:
config: |
Chart Grooming (#14) * Chart Grooming - Changed the default `workflow-controller` installation to use the `ServiceAccount` that is created and bound. - Customized the instanceID logic: - No longer defaults to installed (this was very difficult to see/understand when coming from starter tutorials) - Kept logic to allow for release name or explicit mappings but changed structure a bit - Added in optional configuration for: - CRD Install hook's ServiceAccount to allow clean install if your default roles aren't privledged - Optional Pod and Service annotations - Controller logging level configuration - Minio Customizations - Changed the Secret configuration to properly represent the path of a secret instead of the actual contents - Changed the names of the secret and service that are represented to mirror that of the underlying chart * Adding in role bindings for minio secrets if installed
2018-08-16 00:39:27 -07:00
{{- if .Values.controller.instanceID.enabled }}
{{- if .Values.controller.instanceID.useReleaseName }}
Support using release name for workflow controller instance id
2018-01-05 11:11:40 -08:00
instanceID: {{ .Release.Name }}
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
{{- else }}
Chart Grooming (#14) * Chart Grooming - Changed the default `workflow-controller` installation to use the `ServiceAccount` that is created and bound. - Customized the instanceID logic: - No longer defaults to installed (this was very difficult to see/understand when coming from starter tutorials) - Kept logic to allow for release name or explicit mappings but changed structure a bit - Added in optional configuration for: - CRD Install hook's ServiceAccount to allow clean install if your default roles aren't privledged - Optional Pod and Service annotations - Controller logging level configuration - Minio Customizations - Changed the Secret configuration to properly represent the path of a secret instead of the actual contents - Changed the names of the secret and service that are represented to mirror that of the underlying chart * Adding in role bindings for minio secrets if installed
2018-08-16 00:39:27 -07:00
instanceID: {{ .Values.controller.instanceID.explicitID }}
{{- end }}
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
{{- end }}
Make containerRuntimeExecutor configurable (#36)
2019-06-18 01:33:17 +09:00
containerRuntimeExecutor: {{ .Values.controller.containerRuntimeExecutor }}
Create agro helm chart
2018-01-02 16:45:35 -08:00
artifactRepository:
Updating helm chart and improving style (#7) * 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
2018-06-04 10:39:53 -04:00
{{- if or .Values.minio.install .Values.useDefaultArtifactRepo }}
Add archiveLogs option to Argo workflow controller config map (#32)
2019-05-07 22:45:50 +08:00
{{- if .Values.artifactRepository.archiveLogs }}
archiveLogs: {{ .Values.artifactRepository.archiveLogs }}
{{- end }}
Create agro helm chart
2018-01-02 16:45:35 -08:00
s3:
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
{{- if .Values.useStaticCredentials }}
Create agro helm chart
2018-01-02 16:45:35 -08:00
accessKeySecret:
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
key: {{ .Values.artifactRepository.s3.accessKeySecret.key }}
Chart Grooming (#14) * Chart Grooming - Changed the default `workflow-controller` installation to use the `ServiceAccount` that is created and bound. - Customized the instanceID logic: - No longer defaults to installed (this was very difficult to see/understand when coming from starter tutorials) - Kept logic to allow for release name or explicit mappings but changed structure a bit - Added in optional configuration for: - CRD Install hook's ServiceAccount to allow clean install if your default roles aren't privledged - Optional Pod and Service annotations - Controller logging level configuration - Minio Customizations - Changed the Secret configuration to properly represent the path of a secret instead of the actual contents - Changed the names of the secret and service that are represented to mirror that of the underlying chart * Adding in role bindings for minio secrets if installed
2018-08-16 00:39:27 -07:00
name: {{ .Values.artifactRepository.s3.accessKeySecret.name | default (printf "%s-%s" .Release.Name "minio") }}
Create agro helm chart
2018-01-02 16:45:35 -08:00
secretKeySecret:
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
key: {{ .Values.artifactRepository.s3.secretKeySecret.key }}
Chart Grooming (#14) * Chart Grooming - Changed the default `workflow-controller` installation to use the `ServiceAccount` that is created and bound. - Customized the instanceID logic: - No longer defaults to installed (this was very difficult to see/understand when coming from starter tutorials) - Kept logic to allow for release name or explicit mappings but changed structure a bit - Added in optional configuration for: - CRD Install hook's ServiceAccount to allow clean install if your default roles aren't privledged - Optional Pod and Service annotations - Controller logging level configuration - Minio Customizations - Changed the Secret configuration to properly represent the path of a secret instead of the actual contents - Changed the names of the secret and service that are represented to mirror that of the underlying chart * Adding in role bindings for minio secrets if installed
2018-08-16 00:39:27 -07:00
name: {{ .Values.artifactRepository.s3.secretKeySecret.name | default (printf "%s-%s" .Release.Name "minio") }}
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
{{- end }}
Updating helm chart and improving style (#7) * 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
2018-06-04 10:39:53 -04:00
bucket: {{ .Values.artifactRepository.s3.bucket | default .Values.minio.defaultBucket.name }}
Chart Grooming (#14) * Chart Grooming - Changed the default `workflow-controller` installation to use the `ServiceAccount` that is created and bound. - Customized the instanceID logic: - No longer defaults to installed (this was very difficult to see/understand when coming from starter tutorials) - Kept logic to allow for release name or explicit mappings but changed structure a bit - Added in optional configuration for: - CRD Install hook's ServiceAccount to allow clean install if your default roles aren't privledged - Optional Pod and Service annotations - Controller logging level configuration - Minio Customizations - Changed the Secret configuration to properly represent the path of a secret instead of the actual contents - Changed the names of the secret and service that are represented to mirror that of the underlying chart * Adding in role bindings for minio secrets if installed
2018-08-16 00:39:27 -07:00
endpoint: {{ .Values.artifactRepository.s3.endpoint | default (printf "%s-%s" .Release.Name "minio:9000") }}
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
insecure: {{ .Values.artifactRepository.s3.insecure }}
Add support for S3 artifact keyPrefix (#78)
2019-06-17 12:04:39 -05:00
{{- if .Values.artifactRepository.s3.keyPrefix }}
keyPrefix: {{ .Values.artifactRepository.s3.keyPrefix }}
{{- end }}
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
{{- end}}
add metricsConfig to the configmaps for the workflow-controller-configmap.yaml (#42)
2019-04-16 18:27:40 -04:00
{{- if .Values.controller.metricsConfig.enabled }}
metricsConfig:
{{ toYaml .Values.controller.metricsConfig | indent 6}}{{- end }}
Update Argo to v2.3.0 and add support for Prometheus operator (#73)
2019-07-02 22:41:28 +02:00
{{- if .Values.controller.telemetryConfig.enabled }}
telemetryConfig:
{{ toYaml .Values.controller.telemetryConfig | indent 6}}{{- end }}
[argo] Add workflow persistence configuration (#133)
2019-10-22 17:08:29 -05:00
{{- if .Values.controller.persistence }}
persistence:
{{ toYaml .Values.controller.persistence | indent 6 }}{{- end }}
Reference in a new issue Copy permalink