Xiang Li
this document may help you https://kubernetes.io/docs/concepts/configuration/taint-and-toleration/
Yes, descheduler won't check if pods will be properly evicted to other nodes before evicting, so I think it would make sense to add some mechanism to check this and...
Yes, descheduler should work normally if we got more than one node in cluster available even if we only selected 1 node. I can help fix this, and will submit...
I thought that `Node Selector` is used to select nodes which descheduler can evicts pods from, and it doesn't matter whether these evicted pods will be rescheduled to selected nodes...
So, based on what was discussed above, we can move the parameter `nodeSelector` to `StrategyParameters` and the config file may look like: ```yaml apiVersion: "descheduler/v1alpha1" kind: "DeschedulerPolicy" strategies: "PodLifeTime": enabled:...
@ingvagabund I'm about to refactor [ReadyNodes](https://github.com/kubernetes-sigs/descheduler/blob/d502f059103ca87b69afbffa1f9bc736259a1971/pkg/descheduler/node/node.go#L33) to return all ready nodes in cluster and descheduler will pass all of them to all strategies, then in every strategy we'll select nodes...
@ingvagabund yes, they're basically the same, what I'm suggesting only simplifies the function signature. Selecting nodes will take time to traverse all nodes, but given nodes are stored in memory,...
/kind cleaup /remove-kind bug @seanmalloy @ingvagabund @damemi should we add support for Deployment here?
/kind feature
> Deployment owns a ReplicaSet IINM so setting kind to Deployment will not work. yes, so I'm wondering if we should distinguish `ReplicaSet pods`(created by ReplicaSet) and `Deployment pods`(created by...