-
Story
-
Resolution: Unresolved
-
Major
-
None
-
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
-
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:
HCCO- kube-apiserver (Mulham)
- kube-controller-manager (Mulham)
- CNO
- CCO
- clusterpolicy
- CSI
- CVO
- dnsoperator
- etc
- ignition
- ingress(router)
- ingressoperator
- machineapprover
- nto
- oapi
- oauth
- ocm
- olm
- pkioperator
- registryoperator
- scheduler
- snapshotcontroller
- storage
Example PR to refactor HCCO: https://github.com/openshift/hypershift/pull/4860
docs: https://github.com/openshift/hypershift/blob/main/support/controlplane-component/README.md