2. What is the nature and description of the request?
-> CPMSO, CEO and MCO can enter a deadlocked state when the CPMS and the Control Plane MCP are updated simultaneously. This deadlock state should be avoided or detected by one of the operators instead of relying on the correct ordering of updates to the resource involved.
3. Why does the customer need this? (List the business requirements here)
-> The customer manages OpenShift clusters in a highly automated fashion, partly by implementing the GitOps paradigm to configure clusters. Relying on the order of changes to resources via SyncWaves is, most of the time, a workaround, that should be avoided as much as possible when using GitOps (ArgoCD). Timing/Ordering not only goes against the declarative nature of Kubernetes and OpenShift. Dependency on timing makes operations brittle which in turn leads to increased administrative overhead.
4. List any affected packages or components.
-> CPMSO and MCO