Epic Goal

There are relics of control-plane components left on hosted clusters, including but not limited to empty namespaces, CRDs, etc. Examples are below: 

Namespaces & CRDs

openshift-kube-apiserver Active 87m
openshift-kube-apiserver-operator Active 87m
openshift-kube-controller-manager Active 87m
openshift-kube-controller-manager-operator Active 87m
openshift-kube-scheduler Active 87m
openshift-kube-scheduler-operator Active 87m
openshift-apiserver Active 87m
openshift-apiserver-operator Active 88m
openshift-controller-manager Active 87m
openshift-controller-manager-operator Active 88m

openshiftapiservers.operator.openshift.io 2022-06-30T11:22:33Z
openshiftcontrollermanagers.operator.openshift.io 2022-06-30T11:22:35Z

One way to solve this is to equip the CVO with a profile for HyperShift profile that prevents those relics from being deployed when HyperShift is used.

Why is this important?

As part of decoupling the control plane from workers, we don't want users to be confused by these left-overs, furthermore, it might lead to unexpected behavior if users would create instances for each of these. 

Finally, users look at namespaces with "openshift-*" prefix as control-plane. 

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement
  details and documents.
• ...

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub
  Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub
  Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• 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>