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

• As an openshift administrator i want to scale my pod horizontally based on custom metrics other than CPU/Memory so that my application can scale based on metrics that more align to my application need.  
• In 4.10 the goal is to provide tech preview of KEDA with openshift 

Why is this important?

There are use cases out that require scaling based on metrics that are not either CPU and memory. For example, a database might be scaled based on the number of tables. Customers need more options when it comes to their own, or 3rd party, applications to configure an Horizontal Pod Autoscaler (HPA) object. That way, they can build high uptime and reliability SLOs using every tool available.

An example is scaling an app based on the number of HTTP connections.

Scenarios

1. ...

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. …

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>