-
Epic
-
Resolution: Unresolved
-
Major
-
ACM 2.16.0
-
GH backup & restore
-
Product / Portfolio Work
-
False
-
-
False
-
-
In Progress
-
ACM-26448 - Global Hub 1.7 Component Epics
-
0% To Do, 50% In Progress, 50% Done
Value Statement
Need a statement on how the global hub backup and restore should work when the hubs are managed by a global hub.
Definition of Done for Engineering Story Owner (Checklist)
- Backup and Restore is a TP feature for globalhub.
Design document / documentation on how we expect the user to run a global hub backup and restore for the managed hubs . For example how will the user configure the hub backup on each managed hub and how the backup validation should work if those hubs don't self manage (https://docs.redhat.com/en/documentation/red_hat_advanced_cluster_management_for_kubernetes/2.10/html/business_continuity/business-cont-overview#backup-validation-using-a-policy) - Test validation for the proposed approach
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](
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.