Uploaded image for project: 'OpenShift Container Platform (OCP) Strategy'
  1. OpenShift Container Platform (OCP) Strategy
  2. OCPSTRAT-346

Make Ingress Operator optional

XMLWordPrintable

    • False
    • Hide

      None

      Show
      None
    • False
    • 0% To Do, 0% In Progress, 100% Done
    • L
    • 0
    • Program Call

      Make it possible to entirely disable the Ingress Operator by leveraging the OCPPLAN-9638 Composable OpenShift capability.

      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.

      Scenarios

      1. This feature must consider the different deployment footprints including self-managed and managed OpenShift, connected vs. disconnected (restricted and air-gapped), implications for auto scaling, chargeback/showback use scenarios, etc.
      2. Disabled configuration must persist throughout cluster lifecycle including upgrades

       

            ddharwar@redhat.com Deepthi Dharwar
            ddharwar@redhat.com Deepthi Dharwar
            Mike Fiedler Mike Fiedler
            Ashley Hardin Ashley Hardin
            Ben Bennett Ben Bennett
            Chris Fields Chris Fields
            Votes:
            0 Vote for this issue
            Watchers:
            16 Start watching this issue

              Created:
              Updated:
              Resolved: