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

• The goal is to evangelize the idea to the community to have an option in VPA to select ( among many recommenders) recommender based on the type of workload.

Why is this important?

• It is the first step to add predictive VPA in Kubernetes

Scenarios

1. To enable an advanced VPA recommender that predicts CPU/memory limits/requests based on the behavior of resource usage.
2. To enable a proactive VPA recommender that learns and predicts CPU/memory limits/requests for deep learning training workload.

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. The sig-autoscaling community needs to agree and approve this idea.

Previous Work (Optional):

1. …

Open questions::

1. There are two options to support customized recommenders. 
   1. One is to develop a plugin framework similar to scheduler plugins.
   2. The other is to allow the VPA user to configure recommender as labels/annotations in VPA object, thus the recommender only selects VPA objects based on the label or annotation.

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>