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

Add GA Support for Gateway API via Istio

    XMLWordPrintable

Details

    • Epic
    • Resolution: Unresolved
    • Undefined
    • None
    • None
    • Add GA Support for Gateway API via Istio
    • False
    • None
    • False
    • OCPSTRAT-134Gateway API using Istio for Cluster Ingress - GA
    • Green
    • To Do
    • OCPSTRAT-134 - Gateway API using Istio for Cluster Ingress - GA
    • 0
    • 0% 0%
    • 0
    • 0

    Description

      Epic Goal

      • Add Gateway API via Istio Gateway implementation as GA in future release

      Problem: ** As an administrator, I would like to securely expose cluster resources to remote clients and services while providing a self-service experience to application developers. 

      GA:  A feature is implemented as GA so that developers can issue an update to the Tech Preview MVP and:

      • can no longer change APIs without following a deprecating or backwards compatibility process.
      • are required to fix bugs customers uncover
      • must support upgrading the cluster and your component
      • provide docs
      • provide education to CEE about the feature
      • must also follow Red Hat's support policy for GA

      Why is this important?

      • Reduces the burden on Red Hat developers to maintain IngressController and Route custom resources
      • Brings OpenShift ingress configuration more in line with standard Kubernetes APIs
      • Demonstrates Red Hat’s leadership in the Kubernetes community.

      Scenarios

      1. ...

      Acceptance Criteria

      • Gateway API and Istio Gateway are in an acceptable standing for GA
      • Istio Gateway installation without sidecars enabled
      • Decision completed on whether a new operator is required, especially for upgrade and status reports
      • Decision completed on whether Ingress->Gateway (or Route->Gateway) translation is needed
      • Enhancement Proposals, Migration details, Tech Enablement, and other input for QA and Docs as needed
      • API server integration, Installation, CI, E2E tests, Upgrade details, Telemetry as needed
      • TBD

      Dependencies (internal and external)

      1. OSSM release schedule aligned with OpenShift's cadence, or workaround designed
      2. ...tbd

      Previous Work (Optional):

      1. https://issues.redhat.com/browse/NE-993
      2. https://issues.redhat.com/browse/NE-1036 
      3.  

      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>

      Attachments

        Issue Links

          Activity

            People

              cholman@redhat.com Candace Holman
              cholman@redhat.com Candace Holman
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated: