Ability to space out k8up backups in the same namespace (when there are many pre-backup-pods) about k8up HOT 4 CLOSED

Hi @seanhamlin

Thanks for bringing this to our attention. 30 prebackup pods in a single namespace are quite a lot.

In your linked issue you're writing about spreading the pods over a time of 4 hours. That would also delay the backup by that amount. This also leaves a lot of room for things to change and go wrong. For example if other pods get created or deleted.

As a workaround we thought about a configurable delay between starting each pod. That should give you the ability to space out things as you see fit.

How does that sound to you?

from k8up.

Hi @seanhamlin

Do you have any feedback for my questions above?

from k8up.

Thanks @Kidswiss, yes I would say having an option to stagger the PreBackupPods by even 10 seconds in a given namespace, would yield a much more stable backup process cluster wider.

from k8up.

Hi  @seanhamlin

We discussed this in the team and feel like this won't make sense once we've implemented #316.

Then you have the ability to create multiple schedules per namespace and do the spreading via those.

from k8up.