Feature Overview (aka. Goal Summary)  

As a managed service, ARO, ROSA, which need to be compliant with various regulation may need to force upgrades for customers. Because we are taking this responsibility, there will be a risk that our activity could potentially result in the customer workload/cluster being affected as a result of the upgrade that will be forced on them. In order to mitigate the risk of us breaking the customer's environment, we will need to be able to selectively roll back to a previous version the cluster where our forced upgrade had a negative impact.

<your text here>

Goals (aka. expected user outcomes)

Provide the ability to bring a cluster back to a working state within a few hours of us forcing an upgrade. This would provide us time to have a z stream available with a fix so that we can upgrade the cluster without the negative impacts the customer experienced earlier

Requirements (aka. Acceptance Criteria):

If a customer control plane gets upgrade to a bad z stream, we can roll back that customer's control plane to a previous version.
This is only possible for the Control plane of Hosted control plane, only for service led operations and would not cover the customers workers

<enter general Feature acceptance here>

Anyone reviewing this Feature needs to know which deployment configurations that the Feature will apply to (or not) once it's been completed.  Describe specific needs (or indicate N/A) for each of the following deployment scenarios. For specific configurations that are out-of-scope for a given release, ensure you provide the OCPSTRAT (for the future to be supported configuration) as well.

Use Cases (Optional):

Include use case diagrams, main success scenarios, alternative flow scenarios.  Initial completion during Refinement status.

<your text here>

Questions to Answer (Optional):

Include a list of refinement / architectural questions that may need to be answered before coding can begin.  Initial completion during Refinement status.

<your text here>

Out of Scope

High-level list of items that are out of scope.  Initial completion during Refinement status.

<your text here>

Background

Provide any additional context is needed to frame the feature.  Initial completion during Refinement status.

<your text here>

Customer Considerations

Provide any additional customer-specific considerations that must be made when designing and delivering the Feature.  Initial completion during Refinement status.

<your text here>

Documentation Considerations

Provide information that needs to be considered and planned so that documentation will meet customer needs.  If the feature extends existing functionality, provide a link to its current documentation. Initial completion during Refinement status.

<your text here>

Interoperability Considerations

Which other projects, including ROSA/OSD/ARO, and versions in our portfolio does this feature impact?  What interoperability test scenarios should be factored by the layered products?  Initial completion during Refinement status.

<your text here>