Epic Goal

• the following approach of doing ETCD backup works nice (customer feedback)
  https://github.com/ch-stark/etcd-backup-policy

• we might either do this stable, or move the image to stolostron
• see also: https://github.com/stolostron/policy-collection/issues/199#issuecomment-1021229256  for more information

Why is this important?

           ETCD backup is requested from time to time, it shows nicely the value of Policies

Scenarios

1.   Customer can configure ETCD backup in Git and use PolicyGenerator
     Even some monitoring is contained

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• ...

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. …

Open questions::

    1.   It was based on the ideas of some other repositories, this would need to be
          reviewed

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Downstream documentation merged: <link to meaningful PR>