Epic Overview
In RHOSO 18, Feature package (RHOSO 18.0.x to 18.0.latest) updates are delegated to each of the OpenStack services operators. Each operator should monitor the update and rollback if there was a problem during the process. Implementing a backup before an update would help the roll back and keep the OSP cluster in a healthy and well-maintained state.

Goals
This epic will benefit operators who didn't implement any backup solution at cluster level but still want to be provided with a backup solution at operator level when doing updates.

Requirements

(Optional) Use Cases
< How will the user interact with this epic? >

< Which users will use this and when will they use it? >

< Is this feature used as part of current user interface? >

Out of Scope

Background, and strategic fit
< What does the person writing code, testing, documenting need to know? >

Assumptions
< Are there assumptions being made regarding prerequisites and dependencies?>

< Are there assumptions about hardware, software or people resources?>

Customer Considerations
< Are there specific customer environments that need to be considered (such as working with existing h/w and software)?>

< Are there upgrade considerations that customers need to account for or that the feature should address on behalf of the customer?>

Documentation Considerations
< What educational or reference material (docs) is required to support this epic? For users/admins? Other functions (security officers, etc)? >

< What does success look like?>

< Does this epic have doc impact? Possible values are: New Content, Updates to existing content, Release Note, or No Doc Impact>

< If unsure and no Technical Writer is available, please contact Content Strategy. If yes, complete the following.>

<What concepts do customers need to understand to be successful in [action]?>

<How do we expect customers will use the epic? For what purpose(s)?>

<What reference material might a customer want/need to complete [action]?>

<Is there source material that can be used as reference for the Technical Writer in writing the content? If yes, please link if available. >

<What is the doc impact (New Content, Updates to existing content, or Release Note)?>

Interoperability Considerations
< Which other products and versions in our portfolio does this feature impact?>

< What interoperability test scenarios should be factored by the layered product(s)?>

Questions

References:
https://kubernetes.io/docs/concepts/workloads/controllers/statefulset/#update-strategies
https://developer.ibm.com/articles/support-upgrade-and-downgrade-of-operands-in-kubernetes-operators/
https://www.databricks.com/blog/2022/12/15/scalable-kubernetes-upgrade-using-operators.html
https://github.com/cncf/tag-app-delivery/blob/163962c4b1cd70d085107fc579e3e04c2e14d59c/operator-wg/whitepaper/Operator-WhitePaper_v1-0.md#upgrading-the-operator