Description
When the backup cron job is enabled, the number of backup jobs created is equal to the number of non-backed-up, stopped, non-ephemeral workspaces.
If the number of such workspaces is high (1000 workspaces), then 1000 jobs will start, which can overload the cluster or the image registry.
For prevent such cases, an idea can be to implement a configurable cap, such as 100, which will cap the number of concurrent backup jobs. In this solution, 100 jobs will run, and 900 will be in a queue. Only when a job completes, a new job will be created, until all 1000 backups are complete.
Additional context