-
Story
-
Resolution: Unresolved
-
Major
-
None
-
None
-
None
-
False
-
None
-
False
-
OCPSTRAT-1666 - Ensure Sustainability of the HyperShift Project through Comprehensive Refactor and Standardization of Key Components
-
-
-
Hypershift Sprint 261, Hypershift Sprint 262, Hypershift Sprint 263
-
0
-
0
-
0
User Story:
As a (user persona), I want to be able to:
- As an external dev I want to be able to add new components to the CPO easily
- As a core dev I want to feel safe when adding new components to the CPO
- As a core dev I want to add new components to the CPO with our copy/pasting big chunks of code
Â
https://issues.redhat.com//browse/HOSTEDCP-1801 introduced a new abstraction to be used by ControlPlane components. We need to refactor every component to use this abstraction.Â
Acceptance Criteria:
Description of criteria:
All ControlPlane Components are refactored:
HCCOkube-apiserver (Mulham)kube-controller-manager (Mulham)ocm (Mulham)etcd (Mulham)oapi (Mulham)scheduler (Mulham)clusterpolicy (Mulham)CVO (Mulham)oauth (Mulham)hcp-router (Mulham)storage (Mulham)CCO (Mulham)- CNO (Jparrill)
- CSI (Jparrill)
- dnsoperator
- ignition (Ahmed)
- ingressoperator (Bryan)
- machineapprover
- nto
- olm
- pkioperator
- registryoperator (Bryan)
- snapshotcontroller
Â
Example PR to refactor cloud-credential-operator : https://github.com/openshift/hypershift/pull/5203
docs: https://github.com/openshift/hypershift/blob/main/support/controlplane-component/README.md