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

MicroShift support for GatewayAPI (DevPreview)

XMLWordPrintable

    • Strategic Product Work
    • False
    • Hide

      None

      Show
      None
    • False
    • OCPSTRAT-1131MicroShift Enhancements 2024 for Industrial, Retail and Public Sector edge customers
    • 0% To Do, 33% In Progress, 67% Done
    • L
    • 0

      Feature Overview (aka. Goal Summary)  

      Support the new k8s Gateway API (successor of Ingress) on MicroShift.

      Goals (aka. expected user outcomes)

      K8s GatewayAPI is the new standard to control ingress into a k8s cluster. The goal of this feature is to have this supported on MicroShift.

      As GatewayAPI is still pretty new, we start with a DevPreview for MicroShift to collect feedback from users. 

      Requirements (aka. Acceptance Criteria):

      1. MUST have: full implementation of the  core feature set (incl. conformance testing)
        1. HTTP Route
        2. GRPCRoute
      2. SHOULD have  support of all route types, as esp. for IoT Gateway solutions, non-standard Routes are important:
        1. TLS Route
        2. TCPRoute and UDPRoute
      1. Should support multiple Gateway instances, e.g. for different networks (north/south) or dediecated gateways.
      2. Full support the Use Cases
        1. basic noth/south
        2. Multiple applications behind a single Gateway
      3. Lightweight implementation, consuming as little resources as possible, without adding a full ServiceMesh implementation.
      4. If feasible: an optional installation in addition to the existing IngressControler implementation (HAProxy Router), so that both old Route/Ingress and new HTTPRoute can be used. e.g. "microshift-gatewayapi"

      Questions to Answer (Optional):

      1. can this be delivered in a single release, or do we need a TechPreview phase?

       

      Out of Scope

      tbd

      • Use cases 
        • Basic east/west use case 
        • Gateway and mesh use case
      • Migration from existing Ingress objects to the new API - that is in the responsibility of the admin/user. 

      Background

      GatewayAPI becomes the new defacto standard which offers more flexibility.

      Customer Considerations

      MicroShift customers are requesting this. 

      Documentation Considerations

      MicroShift networking documentation needs to be augmented by examples on how to install and configure GatewayAPI, incl. the in- and out of scope functionalitly.

      Interoperability Considerations

      Should be in-line with OpenShift support of GatewayAPI, re-use the same implementation as much as possible, like with the current Ingress implementation.

       

       

       

       

       

              dfroehli42rh Daniel Fröhlich
              dfroehli42rh Daniel Fröhlich
              John George John George
              Shauna Diaz Shauna Diaz
              Jeremy Peterson Jeremy Peterson
              Pablo Acevedo Montserrat Pablo Acevedo Montserrat
              Daniel Fröhlich Daniel Fröhlich
              Jon Thomas Jon Thomas
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: