af1c9e49c4
Before this change we've assumed a constant time between schedule runs, which is not true for cases like "30 6-16/4 * * 1-5". The fix is to calculate the potential next run using the fixed schedule as the baseline, and then go back one schedule back and allow the cron library to calculate the correct time. This approach saves us from iterating multiple times between last schedule time and now, if the cronjob for any reason wasn't running for significant amount of time. |
||
|---|---|---|
| .. | ||
| config | ||
| metrics | ||
| cronjob_controllerv2_test.go | ||
| cronjob_controllerv2.go | ||
| doc.go | ||
| injection.go | ||
| OWNERS | ||
| utils_test.go | ||
| utils.go | ||