Details
-
Epic
-
Resolution: Unresolved
-
Normal
-
None
-
None
Description
Goal
Move TopologySpreadConstratints - https://kubernetes.io/docs/concepts/scheduling-eviction/topology-spread-constraints/ - to TechPrev by adding docs and qe.
Note: This feature depends on nodes with correct topology informations: https://kubernetes.io/docs/reference/labels-annotations-taints/
Note: API details https://kubernetes.io/docs/reference/kubernetes-api/workload-resources/pod-v1/#scheduling
Note: OCP Docs: https://docs.openshift.com/container-platform/4.11/nodes/scheduling/nodes-scheduler-pod-topology-spread-constraints.html
User Stories
- As a VM owner, I want set topology spread constraints on my VM and VMI, so that they will be scheduled in different AZs
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
Done Checklist
| Who | What | Reference |
|---|---|---|
| DEV | Upstream roadmap issue (or individual upstream PRs) | <link to GitHub Issue> |
| DEV | Upstream documentation merged | <link to meaningful PR> |
| DEV | gap doc updated | <name sheet and cell> |
| DEV | Upgrade consideration | <link to upgrade-related test or design doc> |
| DEV | CEE/PX summary presentation | label epic with cee-training and add a <link to your support-facing preso> |
| 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> |
Attachments
Issue Links
- is blocked by
-
-
- Closed
-