Epic Goal*

Promoting the KDO profile to GA.
 
Why is this important? (mandatory)

The current DevPreviewLongLifecycle operator profile has been in DevPreview for a long time. Promoting the profile is critical for CNV in order to compete better with .. our competition.
 
Scenarios (mandatory) 

Provide details for user scenarios including actions to be performed, platform specifications, and user personas.  

1.  A user is able to specify LongLifecycle instead of DevPreviewLongLifecycle

 
Dependencies (internal and external) (mandatory)

Just renaming the current profile to LongLifecycle.

Contributing Teams(and contacts) (mandatory) 

Our expectation is that teams would modify the list below to fit the epic. Some epics may not need all the default groups but what is included here should accurately reflect who will be involved in delivering the epic.

• Development - The workloads team
• Documentation - The documentation team
• QE - The workloads QE team
• PX - N/A
• Others - N/A

Acceptance Criteria (optional)

LongLifecycle profile is available. DevPreviewLongLifecycle profile is still available.

Drawbacks or Risk (optional)

N/A

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"