chore(dependencies): add better support for fullnameOverride #189
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi,
As far as I can tell, dependencies of the chart currently do not properly support
fullnameOverride
.Given the following
values-local.yaml
file, and helm install commandhelm install redash-euw3 . -f values.yaml -f values-local.yaml
:The deployment environment variables will contain the wrong hosts for both redis and postgres:
Since Helm 3.7 (released August 31, 2021) it's possible to invoke the subchart's named templates that we can use to match the service names. Those changes will not support postgres replication mode, nor redis sentinel, but I feel like those are not currently supported anyway.
Given the same
values-local.yaml
file, secret references will be wrong too. Templates are using the{{ include "redash.fullname" . }}-
prefix which will not match any existing secret in casefullnameOverride
is set forredash
.The error will look like
Warning Failed 4m28s (x12 over 6m38s) kubelet Error: secret "redash-euw3-postgresql" not found
.Finally, the migration job hook uses the
{{ .Release.Name }}-
prefix as a name instead of{{ include "redash.fullname" . }}-
.Those changes do not address any open issue. It's just a problem I ran into. What do you think of those changes ?
Thanks in advance for reviewing.