Value Statement

related to https://issues.redhat.com/browse/ACM-1290

https://issues.redhat.com/browse/ACM-11829

If the local-cluster name can be changed, we need to make sure the hub backup operator still functions properly

• All Placement and PlacementRule resources targeting the hub by using the local-cluster name would have to change. We'll have to update the backup policy placements and use cluster version ( for example ) instead of local-cluster label.

• When you run a hub backup we exclude the local-cluster namespace. We’ll have to find another way of getting the namespace name for the self managed cluster and change the backup operator to work with that.

• Backup-restore is not going to be backward compatible out of the box. If you create a backup on a 2.11 hub where the local-cluster defines the self managed hub and then restore it on a new 2.x hub where that name has changed, any backup resources such as a Placement that targets the local-cluster will not behave the same. We would need to run a post restore operation and update all such resources with the new name.

Definition of Done for Engineering Story Owner (Checklist)

• ...

Development Complete

• The code is complete.
• Functionality is working.
• Any required downstream Docker file changes are made.

Tests Automated

• [ ] Unit/function tests have been automated and incorporated into the
  build.
• [ ] 100% automated unit/function test coverage for new or changed APIs.

Secure Design

• [ ] Security has been assessed and incorporated into your threat model.

Multidisciplinary Teams Readiness

• [ ] Create an informative documentation issue using the Customer

Portal Doc template that you can access from [The Playbook](

https://docs.google.com/document/d/1YTqpZRH54Bnn4WJ2nZmjaCoiRtqmrc2w6DdQxe_yLZ8/edit#heading=h.9fvyr2rdriby),

and ensure doc acceptance criteria is met.

• Call out this sentence as it's own action:

• [ ] Link the development issue to the doc issue.

Support Readiness

• [ ] The must-gather script has been updated.