Deduplicate prune jobs about k8up HOT 4 CLOSED

One idea here:

Add a skipped field to the K8upstatus in the CRD.

If the operator detect already a running prune set the skipped true. Check for that case in the execution worker.

from k8up.

In the case of Lagoon we have the case that multiple namespaces share the same s3 bucket:

• drupal-example-main
• drupal-example-develop
• drupal-example-staging

they all use the bucket baas-drupal-example
There is no specific drupal-example namespace. Therefore each of the namespaces create a backup schedule that includes a prune schedule, therefore having 3 prunes per week. We made sure with random generator that these prunes are not at the same time.
But still pruning 3 times the same bucket is not really useful.

Would this new system also be able to detect this? Like it realizes that there are 3 prunes for the same bucket and it would only run one? Maybe that's also connected to #116 where we would just for all 3 prunes say @weekly and then the operator runs only one prune at a good time per week?

from k8up.

As discussed yesterday in the internal call I'm closing this issue and merge it with #116.

Because we realised that these two features are very closely related and make sense to be implemented together.

from k8up.

This has now moved into #214

from k8up.