[bitnami/superset] fix ingress with extraHosts failed to deploy #33052
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.
Description of the change
The current
.
is thehost
iterator object (range .Values.ingress.extraHosts
), it madeinclude "common.names.fullname" .
failed to evaluate, so we need to assign.
to$root
before loopingextraHosts
Benefits
User can install
bitnami/superset
withingress.extraHosts
Possible drawbacks
N/A
Applicable issues
ingress.extraHosts
#33031Additional information
N/A
Checklist
Chart.yaml
according to semver. This is not necessary when the changes only affect README.md files.README.md
using readme-generator-for-helm