➹ Introduce a concurrency policy option for scheduledScan CRD #275
Description
Is your feature request related to a problem? Please describe.
A scheduledScan should create a scan object about once per execution time of its schedule. We say "about" because there are certain circumstances where two scans might be created, or no job might be created.
In some rare cases it is possible that the scheduledScans controller starts multiple scans in parallel. This for example could lead to resource blocking if the scans couldn't be terminated correctly. In such a situation (time by time) more and more scans will be scheduled and block the cluster resources.
Describe the solution you'd like
It would be great to be able to handle such "blocking cluster resource" situation with a new configuration option for scheduledScans. In some cases it might be useful to allow multiple scan executions and in others not. The give the user more flexibility to configure the scheduledScan behavior it would help to implement a new configuration option concurrencyPolicy as already existing for K8S CronJobs.
A good description can be found here: https://kubernetes.io/docs/tasks/job/automated-tasks-with-cron-jobs/#concurrency-policy
Describe alternatives you've considered
Additional context
Metadata
Metadata
Assignees
Type
Projects
Status