-
Epic
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
None
-
Namespace Scoped PodPlacementConfig and reconciler
-
Future Sustainability
-
50% To Do, 25% In Progress, 25% Done
-
False
-
-
False
-
-
None
-
None
Epic Goal
- To implement a new, namespace-scoped, CR: PodPlacementConfig
- The reconciler will take care of mutating the pod according to the configuration stored in the PodPlacementConfig
Why is this important?
- Users are willing to set different configurations for the preferred affinities related to the architecture in different namespaces for different workloads.
Design document
Scenarios
1. …
Acceptance Criteria
- (Enter a list of Acceptance Criteria unique to the Epic)
- …
Dependencies (internal and external)
1. …
Previous Work (Optional):
1. …
Open questions::
1. …
Done Checklist
- CI - For new features (non-enablement), existing Multi-Arch CI jobs are not broken by the Epic
- Release Enablement: <link to Feature Enablement Presentation>
- DEV - Upstream code and tests merged: <link to meaningful PR orf GitHub Issue>
- DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
- DEV - If the Epic is adding a new stream, downstream build attached to advisory: <link to errata>
- QE - Test plans in Test Plan tracking software (e.g. Polarion, RQM, etc.): <link or reference to the Test Plan>
- QE - Automated tests merged: <link or reference to automated tests>
- QE - QE to verify documentation when testing
- DOC - Downstream documentation merged: <link to meaningful PR>
- All the stories, tasks, sub-tasks and bugs that belong to this epic need to have been completed and indicated by a status of 'Done'.
- is caused by
-
MULTIARCH-4252 As a user I want to setup per-namespace weights for the architectures to be consumed by pods in a mixed cluster
-
- Closed
-
- is cloned by
-
MULTIARCH-5325 As a user I want to setup per-namespace weights for the architectures to be consumed by pods in a mixed cluster [phase2]
-
- New
-