Epic Goal*

Ensure that clusters may be suspended or shut down

 
Why is this important?

This allows customers to use clusters in more complicated scenarios - i.e. save costs when suspended or have cluster ready rapidly instead of installing it every time.

Scenarios

1. HA clusters can be suspended for 90 days
2. Fresh SNO cluster can be shutdown for a year

 
Dependencies (internal and external)

Main deliverable here is the procedure required to gracefully shutdown and restore cluster.

E2e tests will be created which emulate these situation. During e2e test runs found issues are either fixed by respective teams or manual workarounds are added to e2e and the procedure document

Contributing Teams(and contacts)

• Development - vrutkovs@redhat.com 
• Documentation -
• QE - 
• PX - 
• Others -

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 automation. Tests 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”