New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
helm: Correct spire labels indentation #28610
Conversation
Commit 5b80406 does not match "(?m)^Signed-off-by:". Please follow instructions provided in https://docs.cilium.io/en/stable/contributing/development/contributing_guide/#developer-s-certificate-of-origin |
5b80406
to
07d0c72
Compare
Commit 5b80406 does not match "(?m)^Signed-off-by:". Please follow instructions provided in https://docs.cilium.io/en/stable/contributing/development/contributing_guide/#developer-s-certificate-of-origin |
/test |
07d0c72
to
ad449fe
Compare
Additionally, the labels are propagated to pod level as well. Fixes: #28599 Signed-off-by: Tam Mach <tam.mach@cilium.io>
ad449fe
to
fe6cfde
Compare
/test |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good catch! LGTM
@sayboras Could you add a release note to the PR description? Glancing over the changes it looks like it's fixing the labels for SPIRE deployments, so it may be helpful to better highlight that in the release note. |
Thanks and done 👍 |
@sayboras ah, what I meant is that for a user "fixing the indentation" doesn't declare what the side effects are. If this is a cosmetic change then there's no need to backport and it's not a bugfix. If this ensures that when the user configures the feature with setting X or Y, it actually works, then we should document the user impact that way so that users can understand exactly which configurations are affected and decide if the bug is related to their problem or not. And in that case yeah it makes sense to backport this to 1.14. |
Fixes: #28599