-
Notifications
You must be signed in to change notification settings - Fork 70
Remove duplicated label in helm chart: app.kubernetes.io/instance #354
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
Conversation
…tificate.yaml M templates/manager/deployment.yaml Edit#481
Welcome @DiegoLelis! |
Hi @DiegoLelis. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
/assign @Edwinhr716 |
/ok-to-test |
/lgtm |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ahg-g, DiegoLelis The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What type of PR is this?
/kind bug
What this PR does / why we need it
Changes the behaviour of a couple of functions and introduces 2 other functions to make sure the label
app.kubernetes.io/instance
is not set twice.Also fixed the typo on the certificate file name.
Which issue(s) this PR fixes
Fixes #353
Special notes for your reviewer
The previous behaviour added the label
app.kubernetes.io/instance
twice on a few resources.I've tried to keep changes minimal, and to respect the previous design to the best of my ability.
Kept all the previous labels, only removed the duplicated ones.
When choosing to remove between the more generic label, and the more specific one, I choose to deprecate the more generic one.
Tested installing on my cluster with default values and it works.
Does this PR introduce a user-facing change?