NewReconcilableHandler should not be used for BackupConfiguration Informer

[Legion2]

Currently the custom NewReconcilableHandler informer event handler is used to filter the reconciliation events of the BackupConfiguration CR. The "optimization" which only reconciles the BC on changes, has the side effect, that all the resources which are created by the BC (CronJob...) are only updated if the BC is updated. However, if Stash itself is updated to a new version, the BC is not reconciled again resulting in inconsistent configuration for the CronJob resources. In particular, the image version in the CronJob is not updated. Example, I updated to Stash 0.17.0, however the CronJob still uses Stash 0.15.0 container images and the changes introduced in #1396 are not applied to existing CronJobs. However more critical is, that Stash does not reconcile (recreate) the state (CronJob) if someone deleted it, leaving the cluster in an inconsistent state.

Therefore it is better to delete the NewReconcilableHandler and just use a default handler, which periodically reconciles the BC.

stash/pkg/controller/backup_configuration.go

Line 61 in 56eeaba

c.bcInformer.AddEventHandler(queue.NewReconcilableHandler(c.bcQueue.GetQueue(), core.NamespaceAll))

The current workaround is to delete and recreate the BackupConfiguration

[hossainemruz]

Thank you @Legion2 for reporting the issue. We will look into it.