-
Notifications
You must be signed in to change notification settings - Fork 40k
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
allow heapster clusterrole to see deployments #48357
Conversation
Hi @faraazkhan. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with 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. I understand the commands that are listed here. |
Thanks for the fix. Is there an associated issue on https://github.com/kubernetes/heapster? All I see is #48357 which just binds it to this role. If they're going to bind to this, I'd expect the heapster team to update this role as heapster requires new privileges. |
@ericchiang I did not create an issue with heapster, if that is the right thing to do here, I can go do it now. But the issue isn't so much with heapster, like you said, it is simply binding to this role, we just need the role updated. |
/lgtm |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: faraazkhan, liggitt No associated issue. Update pull-request body to add a reference to an issue, or get approval with The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these OWNERS Files:
You can indicate your approval by writing |
/ok-to-test |
Created kubernetes-retired/heapster#1710 for the sake of completeness. |
Automatic merge from submit-queue (batch tested with PRs 48317, 48313, 48351, 48357, 48115) |
What this PR does / why we need it:
Currently the default
system:heapster
ClusterRole does not allow access to thedeployment.extensions
. This limits metric collection and results inDENY
messages in the kube-api logs like these:Which issue this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close that issue when PR gets merged): fixes # kubernetes-retired/heapster#1710Special notes for your reviewer: NONE
Release note: