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 an approach that can be used to disable built-in components of Microshift

Why is this important?

• Some of the built-in components of Micorshift are either not useful by all the users, or there're 3rd-party alternatives that users can choose from.
• We shall allow users to disable some built-in components.

Scenarios

1. A user prefers another loadbalancer implementation (like MetalLB) rather than the one in Microshift.
2. A user doesn't need the mDNS service at all. He wants to disable the mDNS service to save some resources of the host.

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• ...

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. ...

Open questions::

1. We have two options to implement it
   1. put the optional components into separate RPMs, users can choose to enable the components by installing the RPM.
   2. add flags in configuration files to disable the optional components.

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>