Currently Cron tasks are governed by a single lease, so all tasks are executed on whichever pod takes that lease. This change adds a new CronLeaseBehavior parameter to CronModule, making it possible to take out a lease per-cron-task and distribute the tasks across the deployment. The default behavior remains to take out a single lease
Currently Cron tasks are governed by a single lease, so all tasks are executed on whichever pod takes that lease. This change adds a new
CronLeaseBehaviorparameter toCronModule, making it possible to take out a lease per-cron-task and distribute the tasks across the deployment. The default behavior remains to take out a single lease