Bug 1417126

3. What is the nature and description of the request?

PVC from Snapshot

4. How would the customer like to achieve this? (List the functional requirements here)

This feature request is to support in the scenario: We see that this could be addressed in multiple steps:

1) A cluster admin can, given a snapshot ID of a user, create a PV with this snapshot ID, and assign selector labels (as described here https://docs.openshift.com/container-platform/3.4/install_config/persistent_storage/selector_label_binding.html). Kubernetes then would provision this EBS using the specific snapshot. Users would then be able to claims this PV using the given labels.

2) A user should be able, in self service mode, to create a new PV via a PVC fom a snapshot of the underlying storage technology. The user would claim a new PVC given a snapshot ID.
Here we have to make sure that the system knows to which Namespace certain snapshots belong; e.g. by investigating Cloud Provider specific volume to snapshot relationships and K8S's PV to Namespace relationship. 

3) Eventually, we would like for our users to be able to trigger the taking of a snapshot. We could imagine, by setting a new label on a PV e.g. snapshot-state = [requested | ongoing | completed]. By watching this, it could be synched with application logic that ensures that snapshots are consistent. It could then be natural to treat Snapshots as K8S API objects, which policies around their lifecylce. This would allow 2) above not to reference native snapshot IDs, but we could work with K8S labels/selectors

4. Why does the customer need this? (List the business requirements here)

The capability to take snapshots of AWS EBS is a useful and efficient way to back-up application volumes.
In OSCP, we do this regulariy, configured on an AWS level. What is very cumbersome though is to restore such snapshots; in fact, we have not found a proper way to do this.