[bitnami/mlflow] Apply tpl to ingress hostname, external S3 and DB host #36302
+25
−11
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
common.tplvalues.render
anywhere it is referenced iningress.yaml
andingress-tls-secrets.yaml
.common.tplvalues.render
in the S3 helper.common.tplvalues.render
in the DB helper.Benefits
Enhanced Flexibility
Allows for dynamic configuration of resource names (e.g., hostnames, buckets) using Go template syntax like
{{ .Release.Name }}
instead of static values.Improved Chart Reusability
Enables deploying the same chart across multiple environments (e.g., dev, staging) from a single configuration without causing naming collisions.
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