Ted Conbeer
06/29/2021, 4:52 PMvalues.yml
and set the extraManifests value using the --set-file
option, but I'm hitting an error when installing the chart. Not sure what I'm doing wrong. Details in thread. 👉helm-values-local.yml
):
global:
...
dagster-user-deployments:
enabled: true
deployments:
- ...
envSecrets:
- name: local-secret
runLauncher:
...
postgresql:
enabled: true
dagsterDaemon:
...
serviceAccount:
create: true
# We'll use the --set-file option at runtime to add secrets as an extraManifest to this chart
extraManifests: []
helm-secrets-local.yml
):
- apiVersion: v1
kind: Secret
metadata:
name: local-secret
type: Opaque
stringData:
AWS_ACCESS_KEY_ID: mysecretvalue
helm upgrade \
--install dagster dagster/dagster \
--version $DAGSTER_VERSION \
--values ./helm-values-local.yml \
--set-file extraManifests=./secrets/helm-secrets-local.yml
Error: UPGRADE FAILED: template: dagster/templates/extra-manifests.yaml:1:17: executing "dagster/templates/extra-manifests.yaml" at <.Values.extraManifests>: range can't iterate over
- apiVersion: v1
kind: Secret
metadata:
name: local-secret
type: Opaque
stringData:
...
extraManifests:
key to the helm-secrets-local.yml
file, and removing the -
and outdenting the secret definition, but none of those things work)Noah K
06/29/2021, 5:04 PMextraManifests:
- whatever
--values
data togetherTed Conbeer
06/29/2021, 5:04 PMNoah K
06/29/2021, 5:05 PM--set-file
just sets the value as the whole string, not a parsed versionTed Conbeer
06/29/2021, 5:05 PMNoah K
06/29/2021, 5:08 PMTed Conbeer
06/29/2021, 5:09 PM