[feature] clean up objects

[segator]

Yesterday I tried stash for first time, configured auto backup for PVC, and works perfect!
But I saw it creates lot of objects, backupconfiguration, backupsession, empty cronjobs, jobs..

What I expect is after a period of time stash should delete this backup references(BackupSessions).

And If I delete the backupSession object it delete this snapshot from the repository?

[hossainemruz]

What I expect is after a period of time stash should delete this backup references(BackupSessions).

We are going to clean up old BackupSession automatically according to the retention policy.

And If I delete the backupSession object it delete this snapshot from the repository?

No

[segator]

I did some tests, the backupsession is deleted but the job asociated not, if I try to delete it kubectl delete backupsession xxxxxxxxxxxxx, is the same case. Is so ugly see all the objects created through rancher UI, a cronjob for every volume, but no tasks inside, and then a individual job success or failed but stuck there forever.
Jobs created by the backupSession

scheduled Job created by backupConfiguration

Also if for any reason the job can not be executed you will get this

persistentvolumeclaim-plex-xxxx-1565489893   persistentvolumeclaim-plex-xxxx   Running     3d
persistentvolumeclaim-plex-xxxx-1565575210   persistentvolumeclaim-plex-xxxx   Running     2d
persistentvolumeclaim-plex-xxxx-1565661612   persistentvolumeclaim-plex-xxxx   Running     1d
persistentvolumeclaim-plex-xxxx-1565748013   persistentvolumeclaim-plex-xxxx   Running     15h

When I start the node where the volumen exist, what is going to happens? it will try to execute the 4 tasks in parallel? this can be a mess for a backup!

[hossainemruz]

When I start the node where the volumen exist, what is going to happens? it will try to execute the 4 tasks in parallel? this can be a mess for a backup!

Yes. However, only one of them will take backup and others will complete without taking backup.

[hossainemruz]

This issue should be fixed by #907 and will be available in 0.9.0-rc.1 release.