fix: apply additionalLabels also to podSpec #24
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
123BLiN
approved these changes
Jun 11, 2025
gracco
approved these changes
Jun 11, 2025
Collaborator
|
Hey, thank you for your PR. We will revisit this once the initial release using this repository is done. |
Collaborator
|
Hey, I think the chart is finally ready to go. Can you please rebase your PR as we released 0.16.0 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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 patch adds the
additionalLabelsto the podSpec, not just the deploymentSpec. I believe that this approach is the most backwards friendly approach.I checked how other charts use it and it's really a mixed approach. Some have global "labels" and specific "podLabels". Some have "extraLabels" and apply them to all resources.
Solves #21