Skip to content
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.

Sign up for GitHub

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

Jump to bottom

cluster-autoscaler can't update the events of a pod or update the pods status #3144

Closed
BradErz opened this issue Aug 5, 2017 · 0 comments
Closed

cluster-autoscaler can't update the events of a pod or update the pods status #3144

BradErz opened this issue Aug 5, 2017 · 0 comments

Comments

@BradErz
Copy link
Contributor

BradErz commented Aug 5, 2017 •
edited
Loading

With the default addon if the pod can't be scheaduled for whichever reason and the autoscaler tries to update the pod it fails due to lack of rbac permission.

E0805 11:34:43.722542       1 event.go:199] Server rejected event  ..................... 'User "system:serviceaccount:kube-system:cluster-autoscaler" cannot patch events in the namespace "hystrix". (patch events grafana-1238051556-9h6h8.14d7effda08f51bb)' (will not retry!)

E0805 11:24:02.840091       1 utils.go:72] Error during reseting pod condition for hystrix/grafana-1238051556-9h6h8: User "system:serviceaccount:kube-system:cluster-autoscaler" cannot update pods/status in the namespace "hystrix". (put pods grafana-1238051556-9h6h8)
@BradErz BradErz mentioned this issue Aug 5, 2017
Merged
k8s-github-robot pushed a commit that referenced this issue Aug 6, 2017
Merge pull request #3145 from BradErz/fixing-clusterautoscaler-rbac
0942ae3 
Automatic merge from submit-queue

Fixing clusterautoscaler rbac

Fixes #3144 

I have tested on my cluster and it can now update the status of the pods. Im not sure if it also needs the permission to `patch` on the `endpoint`

Maybe someone with better RBAC knowlage can pick up on this? @chrislovecnm 

I also gave the file some pretty treatment.. sorry habbit
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@BradErz