Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Custom licenseKey.secretName not found #41

Open
antonu17 opened this issue Jan 7, 2022 · 0 comments
Open

Custom licenseKey.secretName not found #41

antonu17 opened this issue Jan 7, 2022 · 0 comments

Comments

@antonu17
Copy link

antonu17 commented Jan 7, 2022

Problem

Providing custom licenseKey.secretName makes pods unable to start due to secret not found.

How to reproduce

helm repo add edge-stack https://s3.amazonaws.com/datawire-static-files/charts
helm repo update
helm install edge-stack edge-stack/edge-stack --set licenseKey.secretName=license-secret

Reason

Here .Values.licenseKey.secretName is resolved in the context of the subchart (emissary-ingress), where this value doesn't exist.

volumesRaw: |
- name: {{ include "ambassador.fullname" . }}-secrets
secret:
{{- if and .Values.licenseKey .Values.licenseKey.secretName }}
secretName: {{ .Values.licenseKey.secretName }}
{{- else }}
secretName: {{ include "ambassador.fullname" . }}
{{- end }}

It is possible to get this deployed correctly if both licenseKey.secretName and emissary-ingress.licenseKey.secretName are set like so:

helm upgrade edge-stack edge-stack/edge-stack --set licenseKey.secretName=license-secret --set emissary-ingress.licenseKey.secretName=license-secret

Possible solution

This can be fixed by moving licenseKey parameter to global: block. This will make it available in both edge-stack and emissary-ingress charts context.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant