-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
🐛 fix: (helm/v1alpha1) add missing name prefix and namespace to leader-election-role and leader-election-rolebinding #4357
Conversation
Hi @monteiro-renato. 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. |
be1da7c
to
c331931
Compare
c331931
to
dbaccfb
Compare
…and leader-election-rolebinding
f2913fb
to
26f526a
Compare
Hey 👋, I basically noticed these small inconsistencies when I compared the generated manifests via Kustomize and Helm side by side . |
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.
Really thank you to catcher this one 🥇
We can look in the dist/install.yaml to validate how kustomize
generate the staff: https://github.com/kubernetes-sigs/kubebuilder/blob/master/testdata/project-v4-with-plugins/dist/install.yaml
You are right we should change the name
I hope has no other places.
I think for now is OK we change in the code as you did
We might find better ways in the future
Again thank you a lot for all hard work 🥇
/lgtm
/approve
/ok-to-test
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: camilamacedo86, monteiro-renato 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 |
I'm not sure this is the best approach but since there are already some hardcoded values in there I suppose it's not a terrible idea either.
The Role and RoleBinding do not have a namespace associated with them when the project is
init
ed. I didn't actually try to deploy this but I believe this would actually fail to apply as is (without the namepace on the Role and RoleBinding - src).I added the expected value that a later instruction is expecting.
There are a few other resources that do not have the prefix either. I can open other PRs to address those individually.