You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We use Kubernetes 1.17, which seems to use v1.1.0 for the CronJob controller.
The Kubernetes CronJobs are triggering the jobs as described in the expected behaviour: 2x month only on a weekday and not on a Monday and only on day 10 and 27 of the month is the cron triggered.
We have this schedule:
Expected behaviour
Expected trigger schema in words:
From https://crontab.guru/#0_10_10,27__/2,/3,/4,*/5
Actual behaviour
it triggers as soon as the day of week matches.
We use Kubernetes 1.17, which seems to use v1.1.0 for the CronJob controller.
The Kubernetes CronJobs are triggering the jobs as described in the expected behaviour: 2x month only on a weekday and not on a Monday and only on day 10 and 27 of the month is the cron triggered.
In Argo v2.11.7 robfig/cron/v3 is used.
Here though the "actual behaviour" is observed and the day of month is ignored.
Is that v3 behaviour the "correct" one or is this a bug? Or is there an alternative for our schedule?
The text was updated successfully, but these errors were encountered: