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

• Add configuration option for injecting custom Cert files for MicroShift API endpoint .

Why is this important?

• Customer  esp. in the public sector / defense community have very strict requirements regarding TLS certs. There are frequently intermediate proxies which allow only TLS traffic with certs from accpeted CAs.

Scenarios

1. ...

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• DOC- Documentation for the new configuration fields.

Open questions::

1. do we only replace the external facing API certs, do we keep using the self signed certs for internal communication  ?

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>