You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What is your proposal:
Add a new arg evictAllBarePods to MigrationController to allow evicting pods without OwnerRef no matter it is in Failed phase.
Why is this needed:
Both Kubernetes Descheduler and koord-descheduler has a evictor arg evictFailedBarePods to allow evicting pods with no OwnerRef and in Failed phase. Although these pods won't be re-created by its upper controller, it is in Failed phase so that users can use this arg to allow plugins to evict these pods when knowing there's no risk.
In some special cases, users use some third-party components to make sure that they can re-create pods with no OwnerRef. Under this situation, pods without OwnerRef and are not in Failed phase should also be able to be evicted.
Users now can use the evict annotation to do this. But the annotation let the pod skip all filters. This is not acceptable because users just want to treat them normally. For example, they want to use objectLimiter to restrict the number of evicting pods without OwnerRef, too.
Is there a suggested solution, if so, please add it:
The text was updated successfully, but these errors were encountered:
What is your proposal:
Add a new arg
evictAllBarePods
to MigrationController to allow evicting pods without OwnerRef no matter it is in Failed phase.Why is this needed:
Both Kubernetes Descheduler and koord-descheduler has a evictor arg
evictFailedBarePods
to allow evicting pods with no OwnerRef and in Failed phase. Although these pods won't be re-created by its upper controller, it is in Failed phase so that users can use this arg to allow plugins to evict these pods when knowing there's no risk.In some special cases, users use some third-party components to make sure that they can re-create pods with no OwnerRef. Under this situation, pods without OwnerRef and are not in Failed phase should also be able to be evicted.
Users now can use the evict annotation to do this. But the annotation let the pod skip all filters. This is not acceptable because users just want to treat them normally. For example, they want to use objectLimiter to restrict the number of evicting pods without OwnerRef, too.
Is there a suggested solution, if so, please add it:
The text was updated successfully, but these errors were encountered: