-
Epic
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
enahance-workloadUpdateStrategy
-
To Do
-
100% To Do, 0% In Progress, 0% Done
Goal
Customers wants/needs more control over workloadUpdateStrategy to avoid bad/critical situations on unexpected moments.
Currently workloadUpdateStrategy is fully on/fully off; we can think about
- introducing a cron-like mechanism to let the customer pre-define workloadUpdate windows
- introducing some mechanism to cap the workloadUpdate to reduce the impact on the cluster
- exclude specific VMs based on rules
- ....
User Stories
- High-Level goal-based user story, with context.
"As a <VM Owner/Cluster Admin>, I want <to Achieve Some Goal>, so that <Some Reason/Context>." - another user story
Non-Requirements
- List of things not included in this epic, to alleviate any doubt raised during the grooming process.
Notes
- Any additional details or decisions made/needed
- is caused by
-
CNV-35871 Please review default product behaviour around workloadUpdateStrategy
- Closed
- is related to
-
OCPSTRAT-1026 Admin-defined node disruption policies: Phase 2 (GA)
- Closed
- links to
1.
|
upstream roadmap issue | New | Unassigned | ||
2.
|
upstream documentation | New | Unassigned | ||
3.
|
upgrade consideration | New | Unassigned | ||
4.
|
CEE/PX summary presentation | New | Unassigned | ||
5.
|
test plans in polarion | New | Unassigned | ||
6.
|
automated tests | New | Unassigned | ||
7.
|
downstream documentation merged | New | Unassigned |