-
Notifications
You must be signed in to change notification settings - Fork 532
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
Update rbac.yaml to avoid "Failed to watch" error #285
Conversation
This is to resolve and close issue #271 .
Hi @wangchen615. 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/test-infra repository. |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: wangchen615 The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/assign @Huang-Wei |
/ok-to-test |
/lgtm |
@wangchen615 the root cause is the RBAC rules applied to the secondary scheduler doesn't fully "copy" the ones applied to default scheduler, in particular, access to configmap "extension-apiserver-authentication". This was fixed in the upstream by creating a RoleBinding: kubernetes/kubernetes#72491 So I think we should follow the same way here, instead of imposing a direct configmap access. I raised PR #272 earlier, could you verify if it works? |
Ok, I will close this PR then.
|
This is to resolve and close issue #271 .