Job cleanup does not include Backup objects

[britslampe]

Summary

As "a K8up user"
I want "to enable cleanup for Backups (backup.k8up.io) objects"
So that "I can clean up old/failed K8up Backups"

Context

The Backup objects created from the CRD k8up.io_backups.yaml with the backup controller are not cleaned up after the job is removed if they fail during the prebackup or back phases.

The flag global-failed-jobs-history-limit is already set but is either being ignored or there is another variable that should be set instead to turn on the garbage collection.

Is there another flag that should be set?

Additional Information

• version K8up v2

[Kidswiss]

Hi

Backup objects are only managed and garbage collected by k8up if used together with a Schedule through the schedule controller.

If you manually create Backup objects then this setting won't apply.

[britslampe]

The Backup objects that aren't cleaned up in my case are managed by a schedule. Could there be another error that restic throws in the background that may cause the Backups to hang around?

[britslampe]

An update here, I think that the bug reported from #1005 is the issue happening for me too. Since the job never starts, there's no status for the schedule controller to clean up the objects. So would incrementally upgrading to v4 resolve this? It was mentioned that the latest version should have a resolution.