This is for advanced use cases where users wants to provide their own system.yaml
to configure Pipelines. This overrides the existing system.yaml
in the values.yaml
.
systemYamlOverride: ## You can use a pre-existing secret by specifying existingSecret existingSecret: ## The dataKey should be the name of the secret data key created. dataKey:
Note
From chart version 2.2.0 and above, the .Values.existingSecret
is changed to .Values.systemYaml.existingSecret
and .Values.systemYaml.dataKey
.
From chart version 2.3.7 and above, the .Values.systemYaml
is changed to .Values.systemYamlOverride
.
helm upgrade --install pipelines --namespace pipelines jfrog/pipelines -f values-external-systemyaml.yaml