Mike Dame
Mike Dame
Would definitely like to get more feedback from the scheduling sig on the feasability of this. Getting "actual" pod usage has been a tricky problem I've personally hit trying to...
/remove-lifecycle stale
@Stefik95 the linked enhancements around real load aware scheduling are still being worked on (mainly in the scheduler-plugins repo, under the "Trimaran" name). It was mentioned above, but getting actual...
Right now, the strategy calculates usage based on the requests in the pod spec (and it re-lists the pods each time). I'm not sure if you can actually edit pod...
Ah, yes descheduler will only see the value that is set in the pod spec. In that example, 500m. Actual usage such as that is what we need metrics for...
Right now there hasn't been much work done for this in descheduler, but like I said we can start looking at what kind of metrics access we would need and...
Is this being actively worked on? https://github.com/kubernetes-sigs/descheduler/issues/538 mentioned that there is a possible solution they would like to propose
Hi @mczimm, We talked about this in slack, but to continue the discussion here for visibility: the `maxSkew=2` constraint is already balanced when the third AZ comes back up and...
@mczimm let's open another issue for that and close this one as fixed. I don't think that metric will really be the right place for that kind of label, but...
Does just setting it to exclude `ReplicaSet` cover the case here then? I guess for ease-of-use we could internally replace `Deployment` with `ReplicaSet` which would be a small change. The...