Uploaded image for project: 'Network Edge'
  1. Network Edge
  2. NE-1129

Composable OpenShift: Make ingress optional on HyperShift



    • Composable OpenShift: Make ingress optional on HyperShift
    • 31
    • False
    • None
    • False
    • To Do
    • OCPSTRAT-346 - Make Ingress Operator optional
    • OCPSTRAT-346Make Ingress Operator optional
    • 32
    • 32% 32%
    • L
    • 0
    • 0.0


      OCP/Telco Definition of Done
      Epic Template descriptions and documentation.


      RFE: https://issues.redhat.com/browse/RFE-3395

      Enhancement PR: https://github.com/openshift/enhancements/pull/1415

      API PR: https://github.com/openshift/api/pull/1516

      Ingress  Operator PR: https://github.com/openshift/cluster-ingress-operator/pull/950


      Feature Goal: Make it possible to entirely disable the Ingress Operator by leveraging the Composable OpenShift capability.

      Epic Goal

      Implement the ingress capability focusing on the HyperShift users.


      • Fully implement the ingress capability on the standalone OpenShift.


      As described in the EP PR.

      Why is this important?

      • For Managed OpenShift on AWS (ROSA), we use the AWS load balancer and don't need the Ingress operator. Disabling the Ingress Operator will reduce our resource consumption on infra nodes for running OpenShift on AWS.
      • Customers want to be able to disable the Ingress Operator and use their own component.


       # ...

      Acceptance Criteria

       * Release Technical Enablement - Provide necessary release enablement details and documents.
       * Ingress Operator can be disabled on HyperShift.

      • Dependent operators and OpenShift components can tolerate the disabled ingress operator on HyperShift.

      Dependencies (internal and external)

       # The install-config and ClusterVersion API have been updated with the capability feature.
       # The console operator.

      Previous Work (Optional):

      Open questions:


      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>


        Issue Links



              alebedev@redhat.com Andrey Lebedev
              mfisher1@redhat.com Michael Fisher
              Hongan Li
              Melvin Joseph Melvin Joseph
              Kevin Owen Kevin Owen
              0 Vote for this issue
              11 Start watching this issue