[bitnami/drupal] templates/ingress.yaml: fix wrong www.www tls name #29564
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
This should fix the issue mentioned in #29190, which impacts the nginx, wordpress and drupal charts.
Benefits
It should now be possible to use an ingress.hostname value of www.example.com and set the nginx.ingress.kubernetes.io/from-to-www-redirect annotation, without a TLS host for www.www.example.com being added.
Checklist
Chart.yaml
according to semver. This is not necessary when the changes only affect README.md files.