Store backup CRs with Application

CRs should be stored with the application namespace so they are versioned with application and backed up as part of the namespace backup. Storing the backup CRs with the Backup namespace means restore is limited to clusters that are manage by the Fusion backup. Storing with the application namespace makes backup as "mobile" as the application.

Disclaimer: I am technical sales, not hands-on. I have been presenting Backup as Code concept to current OpenShift customers. Scenarios came up in discussions that I don't believe we can support with the current architecture. Happy to be wrong.

Scenario 1: Develop environment is separate from production, could be completely different platform i.e dev on the cloud and production on-prem. Backup of each environment is managed by a separate installation of the Fusion (2.6) Backup management console. Developer creates Backup CR for the application, tests B/R in the test environment. App is ready to move to production. Backup CR goes to the production environment with the app.

Scenario 2: Primary DC is lost including Fusion Backup management console. Application backed up to S3 offsite. Customer wants to restart app on existing OpenShift environment with separate Fusion backup manager. Need way for Fusion Backup manager at the alternate site to recover the application.

Scenario 3. Changes in the customer application between V1 and V2 require changes in the Backup CR. Customer needs to do recover V1 to perform regression testing, need the V1 BackupCR to perform the restore.