Epic Goal

• To split the controllers for the cluster-scoped ClusterPodPlacementConfig and  namespace-scoped PodPlacementConfig
• To update the operator so that it can handle the lifecycle of the PodPlacementConfig in each namespace

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, as implemented by MULTIARCH-5280
• Having separate controllers allow better control, safety and security for users, especially in environments where the users can manage the namespace owning the PodPlacementConfig, but can't have access to the main namespace where the operator is deployed.

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'.