[bitnami/keycloak] Fix: Rename duplicated secret labels #36254
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.
this commit 0941bbc introduced duplicated label
app.kubernetes.io/component
, which breaks strict YAML validation.I think the desired output was meant to have these two labels:
Description of the change
Rename the duplicated lables from
to
Benefits
Working YAML validation, on our end we use Kustomize for so much of our applications, and when we build helm based apps using chart version 25.2.0, we have this issue:
and after some digging, I found it was due to
tls-pass-secret.yaml
template having two identical components' label.Possible drawbacks
Applicable issues
Additional information
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