Loading...

XML

Word

Printable

Type: Feature
Resolution: Unresolved
Priority: Normal
Fix Version/s: None
Affects Version/s: None
Component/s: Autoscaling, Core
Labels:

Activity Type:
Product / Portfolio Work
Parent Link:
None
Hierarchy Progress Bar:

0% To Do, 33% In Progress, 67% Done
Blocked:
False
Blocked Reason:
None
Ready:
False
Size:
S

Target Version:

openshift-4.21
Release Blocker:
None

SFDC Cases Counter:
SFDC Cases Open:
SFDC Cases Links:

PX Review Complete:
PX Priority Data:
PX Impact Score:
PX Technical Impact:
None
PX Impact Range:
None
PX Scheduling Request:
None
PX Technical Impact Notes:
None

Release Note Text:
Undefined

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

blocks

CNV-7384 DP: Memory Hotplug