Add bucket prefix and in-place/remote env variables for restores

[sync-by-unito[bot]]

The Medusa restore init containers need following new env variables to be set:

• Bucket prefix: path prefix to point to another cluster's backups in the storage bucket
• In Place/Remote: flag indicating whether the performed restore is in-place or remote.

These values will then be used to invoke medusa.restore_node in the medusa-restore init container. The init-container needs to deal with mapping between source and dest topologies to self determine which backup it needs to restore. Pre-checks in the operator will guarantee that a 1:1 mapping is possible and topologies are compatible.

┆Issue is synchronized with this Jira Story by Unito ┆Issue Number: K8OP-140

[sync-by-unito[bot]]

➤ Karan Dhingra commented:

Alexander Dejanovski - looks like you are working on it, so I’m assigning this to you 😉

[adejanovski]

Restores are only possible if a corresponding MedusaBackup object exists locally. It seems challenging then to perform a restore on a different prefix than the one set in Medusa's settings. That would involve doing a sync on a different prefix prior to restoring, which also means we'd need to make it possible for a sync to use a different prefix. In the end, that would create quite a lot of confusion as we'd sync objects that don't belong here on the longer term. @jsanda, I think we should send that issue back to investigation for now so that we can agree on whether or not we want this.