We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
What is your proposal:
call eviction API before kill container
Why is this needed:
memoryEvict will kill container then call eviction api, this may disobey pod disruption budgets (PDB)
koordinator/pkg/koordlet/qosmanager/plugins/memoryevict/memory_evict.go
Line 163 in 661dd71
Is there a suggested solution, if so, please add it:
if eviction response OK, then we kill pod/container, otherwise skip. refer https://kubernetes.io/docs/concepts/scheduling-eviction/api-eviction/#how-api-initiated-eviction-works
There is a bonus with call eviction API first, we can disable eviction by update rolebinding.
The text was updated successfully, but these errors were encountered:
reference https://github.com/kubernetes/kubernetes/blob/d61cbac69aae97db1839bd2e0e86d68f26b353a7/test/integration/evictions/evictions_test.go#L126C5-L127C13
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
What is your proposal:
call eviction API before kill container
Why is this needed:
memoryEvict will kill container then call eviction api, this may disobey pod disruption budgets (PDB)
koordinator/pkg/koordlet/qosmanager/plugins/memoryevict/memory_evict.go
Line 163 in 661dd71
Is there a suggested solution, if so, please add it:
if eviction response OK, then we kill pod/container, otherwise skip. refer https://kubernetes.io/docs/concepts/scheduling-eviction/api-eviction/#how-api-initiated-eviction-works
There is a bonus with call eviction API first, we can disable eviction by update rolebinding.
The text was updated successfully, but these errors were encountered: