OCP/Telco Definition of Done
Epic Template descriptions and documentation.

Epic Goal

• Provide a UX experience for admins to see the health/status/version of their platform operators
• Provide a UX experience for admins to explicilty upgrade their platform operators
• Provide a UX experience for admins to install/uninstall a platform operator

Why is this important?

• Platform operators are closer to a "first class citizen" of a cluster (more like a cluster operator than a traditional olm operator, in terms of importance). They have unique lifecycle flows that aren't sufficiently covered by the existing OLM experience, and involve new api objects (which will wrap the underlying olm flows)

See the platform operator design doc here:
https://docs.google.com/document/d/1qwbrvokZq9LSRm_4NKNAHKa6i0Wsaw6I8-E09v13xH8/edit

And an early EP here:
https://github.com/openshift/enhancements/pull/1170

and here:

Scenarios

1. See goals above

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• Admin can see the state of their platform operators (conditions, versions, health)
• Admin can install/uninstall a platform operator
• Admin can choose to upgrade a platform operator

Dependencies (internal and external)

1. Dependent on the olm platform operator api implementation

Previous Work (Optional):

1. Existing cluster operator and olm operator interfaces

Open questions::

1. …

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Downstream documentation merged: <link to meaningful PR>