Jan Chaloupka f26ab740fe feat(pkg/descheduler): do not cancel the context when runDeschedulerLoop fails ...

When the descheduler is running in the dry mode the the kube client sandbox restoring may fail.
Which can be caused by timeouts when waiting for internal caches to sync.
The internal timeouts depend on the cluster size which changes in time.
No reason to cancel the context because of that.

2026-02-03 23:31:06 +01:00

..

api

chore: make gen

2026-01-04 20:23:13 +01:00

apis/componentconfig

chore: make gen

2026-01-04 20:23:13 +01:00

descheduler

feat(pkg/descheduler): do not cancel the context when runDeschedulerLoop fails

2026-02-03 23:31:06 +01:00

features

Define EvictionsInBackground feature gate

2024-11-14 13:29:59 +01:00

framework

add namespaceLabelSelector

2026-02-02 15:22:11 +03:00

tracing

fix: provide USER env var to correctly initialize tracing

2025-11-15 01:40:08 -05:00

utils

fix: pod resource calculation to consider native sidecars

2025-11-01 10:48:00 -04:00

version

fix: minor version parsing in version compatibility check

2024-07-28 11:44:12 -04:00