Max Scan Concurrency

[janbro]

Adds cross-pod concurrency limiting for external scanners using a periodic dispatcher backed by the shared database. A recurring JobRunr job claims QUEUED jobs in FIFO order up to a configurable max-concurrency per scanner, preventing overload on external scanning services. Startup and watchdog recovery handle concurrency-limited scanners without interfering with the dispatcher.

Two additional configuration properties for configured scanners:

ovsx:
  scanning:
    configured:
      my-scanner:
        max-concurrency: 4           # max simultaneous jobs across all pods
        max-queue-wait-minutes: 120   # fail queued jobs after this long

• max-concurrency - Maximum simultaneous jobs (PROCESSING + SUBMITTED) for this scanner across all pods. A periodic dispatcher promotes QUEUED jobs in FIFO order up to this limit. Set to -1 (default) for unlimited.
• max-queue-wait-minutes - Maximum time a job may sit in QUEUED before being marked FAILED. Only relevant when max-concurrency is positive. Prevents unbounded queue growth if the external service is down. Defaults to 120 minutes.

[netomi]

Creation of the indices in the ScannerJob entity might require a db migration, need to test that first

[netomi]

can you allow maintainers to push to the branch or resolve the conflicts yourself?

[janbro]

Just resolved the conflict. For some reason not seeing the option to allow maintainers to edit

[janbro]

resolving the ci error

[netomi]

the additional index needs a db migration, will add it accordingly, there are also other things that are out of sync