Uploaded image for project: 'OpenShift Hosted Control Plane'
  1. OpenShift Hosted Control Plane
  2. HOSTEDCP-2040

Refactor CPO Components to use the new abstraction

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • None
    • None
    • 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:

      • HCCO
      • kube-apiserver (Mulham)
      • kube-controller-manager (Mulham)
      • ocm (Mulham)
      • etcd (Mulham)
      • oapi (Mulham)
      • CNO (Jparrill)
      • CCO
      • clusterpolicy
      • CSI (Jparrill)
      • CVO
      • dnsoperator
      • ignition (Ahmed)
      • ingress(router)
      • ingressoperator (Bryan)
      • machineapprover
      • nto
      • oauth
      • olm
      • pkioperator
      • registryoperator (Bryan)
      • scheduler (Ahmed)
      • 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

              rh-ee-mraee Mulham Raee
              rh-ee-mraee Mulham Raee
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: