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

<--- Cut-n-Paste the entire contents of this description into your new Epic --->

Epic Goal

• Provide a controlled and supported way to use FeatureGates (from k8s and OpenShift)  

Why is this important?

• Users are able to use FeatureGates with MicroShift, while default features gates in Microshift are well aligned with what is inherited from OpenShift.

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• Users must be able to configure / enable feature gates in a controlled and deterministic way. For example the CPUManager  prefer-align-cpus-by-uncorecache alpha/beta feature. (see OCPSTRAT-2333)

Dependencies (internal and external)

1. TBD

Previous Work (Optional):

1. USHIFT-2813

Open questions::

1. TBD

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>