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

Note: this epic tracks upstream work and does not require QE, documentation or TE.

1. Proposed title of this feature request
VPA requires reboot of pod to apply new CPU/Memory parameter

2. What is the nature and description of the request?
As a OCP admin i want my pods to scale without disruption so that it does not effect the workload

3. Why does the customer need this? (List the business requirements here)
Met with SAS customer . they are running DB in a container and wants to scale up during peak workload without disruption

4. List any affected packages or components.

notes
https://github.com/kubernetes/kubernetes/issues/67500

Why is this important?

• …

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>