Value Statement

If using the volsync to backup PVC's the PVC should be able to freeze before a snapshot is taken and unfreeze after that.

We need some hooks to allow for that 

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

VolSync will not be doing hooks as the permissions required to do this are quite vast and can potentially give users who have access to volSync in a namespace permisions to execute potentially anything they want on any pod in the namespace.

Instead, we've looked at annotations on the PVC - To allow applications/controllers to be able to coordinate when VolSync can run a snapshot/clone within a sync cycle. This can allow the app (such as global hub) to quiesce their app, tell volSync to proceed with the snapshot, then unquiesce once volsync has completed taking the snapshot. 

Changes have been merged upstream - doc to cover the steps done upstream:

Annotation-coordination.md

Definition of Done for Engineering Story Owner (Checklist)

• Come with resolution on the feasibility for such support in volsync

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.