Epic Goal*

In https://issues.redhat.com/browse/ETCD-81 we delivered a tech-preview API to configure periodic and one-time backups saved to a user specified PersistentVolume PV.

This epic targets the GA of that API and feature.

 
Why is this important? (mandatory)

OCP customers can benefit from the ability to configure a day-2 setup of automated backups.

Scenarios (mandatory) 

An admin should be able to configure automated and one time backups via the API and see their backups saved to their specified PV with the desired retention policy.

An alert should be generated if there is a failure to backup per the schedule.

 
Dependencies (internal and external) (mandatory)

One thing we have to investigate and decide upon is whether we would want to first have a no-config option for automated backups saved to local disk across the control-plane nodes. 
If we do, then that would be a separate epic that has to be delivered before the GA of the API.

It may be the case that this no-config enhancement to the feature will have no impact on the API in which case we can GA the existing tech-preview feature and implement the no-config option as a follow up.

Contributing Teams(and contacts) (mandatory) 

Our expectation is that teams would modify the list below to fit the epic. Some epics may not need all the default groups but what is included here should accurately reflect who will be involved in delivering the epic.

• Development - etcd team
• Documentation - etcd docs, Kevin Owens
• QE - etcd QE, Sandeep Kundu
• PX - 
• Others -

Acceptance Criteria (optional)

See the GA requirements and test plan from the enhancement
https://github.com/openshift/enhancements/blob/master/enhancements/etcd/automated-backups.md#test-plan

Drawbacks or Risk (optional)

Done - Checklist (mandatory)

The following points apply to all epics and are what the OpenShift team believes are the minimum set of criteria that epics should meet for us to consider them potentially shippable. We request that epic owners modify this list to reflect the work to be completed in order to produce something that is potentially shippable.

• CI Testing -  Basic e2e automationTests are merged and completing successfully
• Documentation - Content development is complete.
• QE - Test scenarios are written and executed successfully.
• Technical Enablement - Slides are complete (if requested by PLM)
• Engineering Stories Merged
• All associated work items with the Epic are closed
• Epic status should be “Release Pending”