Mike Dame
Mike Dame
Hi @hanumanthan, very sorry but I haven't been able to take a deep look yet. I will prioritize that this or next week. In the meantime, could you please remove...
@Svisstack no, this PR is to add a new version for the Descheduler's own config API Your error is that your cluster is not recognizing the `v1` CronJob type. What...
/remove-lifecycle stale
This seems like a bug to me, probably this line was carried over from LowNodeUtilization where a check like this makes more sense. But the point of HighNodeUtilization is to...
@slobo automatically cordoning the nodes is an interesting idea. I believe cordon drains the nodes with respect to PDBs, which aligns with our use of the eviction API. Though there...
@slobo yeah good point, bumped that issue because someone had expressed interest in updating the docs (though sometimes these things get buried)
> I wonder how many least-utilized nodes should we evict from, how many higher nodes should we target? (taking into account not just the case where all the nodes are...
> > I also would not recommend it as a method to bypass a proper scheduler configuration > > My use case is that nodes were properly provisioned at the...
Some more info on what I mean: there aren't any tests that currently make sure the written/generated resources in `gmp-system` are actually monitored and reconciled on any changes that deviate...