Value Statement

Blog Idea 1:
1. Defining your SLA for Backup and Restore

if Hub goes does:
1. do you have workload on Hub
2. do you have critical alerts on Hub
3. do you have hosted control planes
4. do you have Gitops as push model
.....

When do you determine that Cluster cannot be restored?
Discuss Automatic option
Do you need standby Cluster?
Can you install Cluster just after outage

Blog Idea 2: Work out extended Runbook we did for customers last weeks

Blog Idea 3: Highlight all DR Policies in policy-collection-repo + Virt

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_issue template](
  https://github.com/stolostron/backlog/issues/new?assignees=&labels=squad%3Adoc&template=doc_issue.md&title=),
  and ensure doc acceptance criteria is met. Link the development issue to
  the doc issue.
• [ ] Provide input to the QE team, and ensure QE acceptance criteria
  (established between story owner and QE focal) are met.

Support Readiness

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