Skip to content

Conversation

@fentonfentonfenton
Copy link

@fentonfentonfenton fentonfentonfenton commented Aug 23, 2023

actually just followed this PR in an unrelated kubernetes repo: https://github.com/kubernetes-sigs/descheduler/pull/64/files

was getting an error:

{"error":"pods \"{REDACTED}\" is forbidden: User \"system:serviceaccount:{REDACTED}:pod-reaper-service-account\" cannot create resource \"pods/eviction\" in API group \"\" in the namespace \"uat-nucleus\"","message":"unable to delete podpods \"{REDACTED}\" is forbidden: User \"system:serviceaccount:{REDACTED}pod-reaper-service-account\" cannot create resource \"pods/eviction\" in API group \"\" in the namespace \"{REDACTED}s\"","pod":"{REDACTED}","severity":"warn","time":"2023-08-23T00:05:01.423715449Z"}", "logtag":"F", "stream":"stderr", "tag":"{REDACTED}T"}

@brianberzins
Copy link
Contributor

Is your use case specifying the EVICT configuration?
If not, it feels really odd that this permission would be needed.
If it is using the EVICT configuration this would make perfect sense and I should update the readme to make it easier to understand!

@fentonfentonfenton
Copy link
Author

Is your use case specifying the EVICT configuration? If not, it feels really odd that this permission would be needed. If it is using the EVICT configuration this would make perfect sense and I should update the readme to make it easier to understand!

yep. using evict :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants