Uploaded image for project: 'OpenShift Request For Enhancement'
  1. OpenShift Request For Enhancement
  2. RFE-3395

Make Ingress Operator optional

    XMLWordPrintable

Details

    • False
    • None
    • False
    • Not Selected
    • OCPSTRAT-147 - OpenShift Optional Capabilities (Phase 3)
    • 0
    • 0% 0%
    • OCPSTRAT-147OpenShift Optional Capabilities (Phase 3)

    Description

      Epic Goal

      • 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.
      3.  

      Acceptance Criteria

      • CI - MUST be running successfully with tests automated
      • Release Technical Enablement - Provide necessary release enablement details and documents.
      • ...

      Dependencies (internal and external)

      1. ...

      Previous Work (Optional):

      1. …

      Open questions::

      1. …

      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>

       

       

      Attachments

        Issue Links

          depends on

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. NE-1151 AWS ALB operator GA

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed
          is blocked by

          Feature - Capability or a well-defined set of functionality that delivers business value. Features can include additions or changes to existing functionality. Features can easily span multiple teams, and potentially multiple releases. OBSDA-278 Don't block Cluster Monitoring Operator if Routes aren't accepted

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • In Progress
          is cloned by

          Feature - Capability or a well-defined set of functionality that delivers business value. Features can include additions or changes to existing functionality. Features can easily span multiple teams, and potentially multiple releases. OCPSTRAT-346 Make Ingress Operator optional

          • Critical - To be worked on immediately following BLOCKER issues.
          • In Progress
          is related to

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. NE-1129 Composable OpenShift: Make ingress optional on HyperShift

          • Critical - To be worked on immediately following BLOCKER issues.
          • In Progress
          relates to

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. HOSTEDCP-732 [Spike] Making Ingress operator optional

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • In Progress
          links to

          GitHub openshift/enhancements#1415: NE-1129: Make ingress operator optional on HyperShift

          Activity

            People

              ddharwar@redhat.com Deepthi Dharwar
              julim Ju Lim
              Votes:
              0 Vote for this issue
              Watchers:
              15 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: