Ukri Niemimuukko
Ukri Niemimuukko
@RyanDevlin at least I'd like to see this bug sorted one way or the other. I like the nodeFit feature and I'd like to be able to use it with...
@damemi @ingvagabund this seems to have been left without a decision and thus Ryan hasn't been able to work on this. @RyanDevlin are you still active on those patches of...
> The 2nd option is more preferable @ingvagabund please review #793. And perhaps somebody could trigger ok-to-test?
> For backward compatibility every v1alpha1 strategy configuration will be converted in a separate v1alpha2 profile internally. In case of `RemovePodsViolatingNodeAffinity` strategy/plugin, the backward compatible setting will correspond to: >...
The health-demo predates the nodeFit feature of the descheduler. You might want to turn nodeFit off in your descheduler configuration, and see if that helps a bit. Based on a...
Filed to the descheduler project, we'll see what the solution will be: https://github.com/kubernetes-sigs/descheduler/issues/863
> Thanks! I also noticed that the nodeFit flag is not taking effects, but good news is that posting the extended resource to all work nodes would solve the problem...
GAS doesn't take any pod affinity rules into consideration, and it shouldn't, as there is another scheduler component (plugin) responsible for filtering nodes that would violate pod affinity rules. It...
@briandealwis any chance of getting this merged? This would probably unblock #133 which is long due. Buildkits give nasty warning messages while debugging anything that requires go 1.21.