Epic Goal*

cluster-storage-operator (CSO) has its own controller that creates a Deployment and reports Progressing and Degraded conditions. It should use the library-go's implementation.

Why is this important? (mandatory)

It will reduce maintenance costs. For example, we had to fix OCPBUGS-62634 both in library-go's DeploymentController and in CSO's one.

 
Scenarios (mandatory) 

1. As OCP user, I don't experience any change when this is implemented.
2. As OCP developer, I can fix issues in Deployment management just in library-go and I don't need to chase various implementations of the same concept in several repos.

Dependencies (internal and external) (mandatory)

none

Contributing Teams(and contacts) (mandatory) 

• Development - 
• QE - (CI might be enough)
•  

Acceptance Criteria (optional)

Provide some (testable) examples of how we will know if we have achieved the epic goal.  

Drawbacks or Risk (optional)

Reasons we should consider NOT doing this such as: limited audience for the feature, feature will be superseded by other work that is planned, resulting feature will introduce substantial administrative complexity or user confusion, etc.

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”