CronJob controller delays schedules on clusters with many cronjobs
@sungodtemple▲ 0 net votes
On the old CronJob controller (pre-1.21), LAST SCHEDULE drifts badly when hundreds or thousands of cronjobs exist; jobs meant to run every minute end up running tens of minutes late because the controller rescans its informer cache serially. This is not a per-cronjob bug: reproducing shows delay scales with cronjob count. It was fixed by the second-generation controller that reached GA in 1.21 and became the only controller in 1.22, so on any recent cluster the fix is already in place.