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

[GWAPI-TP] Provide a solution for a Unified Control Plane

    XMLWordPrintable

Details

    • Epic
    • Resolution: Won't Do
    • Undefined
    • None
    • None
    • Provide a solution for a Unified Control Plane
    • 8
    • False
    • None
    • False
    • To Do
    • OCPSTRAT-247 - Gateway API using Istio for Cluster Ingress - Tech Preview
    • OCPSTRAT-247Gateway API using Istio for Cluster Ingress - Tech Preview
    • 0
    • 0% 0%
    • 0
    • 0.0
    • Approved

    Description

      Blocker issue for Tech Preview

      User story: As a service mesh and gateway API administrator, I need functionality for an operator that can automatically configure what is needed after I create a Gateway and HTTPRoute , in order to get a result that certain ingress traffic gets routed into the mesh per the httproute object and gets routed within the mesh per the mesh configuration. 

      On an OpenShift cluster that runs both OSSM and a cluster-ingress-operator managed GWAPI, design a solution that runs without the need for two separately administered control planes.  Some requirements:

      • Provides Gateway API ingress for applications (even if there is no service mesh)
      • Provides a solution (document or otherwise) for when Gateway API is there first, and service mesh is added later.
        • Discuss options with service mesh team
        • Answer NE-1178
      • Provides a solution for when service mesh is there first, and Gateway API is added later (we have tested and this seems to be working fine)
        • If service mesh is already installed, may need to reconfigure portions to fit Unified Control Plane requirements

      Attachments

        Issue Links

          depends on

          Spike - Represents a research-related task. NE-1074 Understand whether Istio Gateway API and Istio can run in same control plane

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed
          is blocked by

          Sub-task - The sub-task of the issue NE-1178 Answer: Do we need to integrate with an existing service-mesh control-plane?

          • Critical - To be worked on immediately following BLOCKER issues.
          • To Do
          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-1105 Provide a solution for Gateway management by an operator

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. NE-1291 [TBD] Implement SMCP customization

          • Undefined - Priority not specified.
          • To Do

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. NE-1107 Provide a solution for DNS Management

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

          Spike - Represents a research-related task. NE-1139 Design discussion for switching into and out of service mesh and maintaining a single control plane

          • 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.
          • To Do

          Spike - Represents a research-related task. NE-1290 Define the options list and API to configure the SMCP created by cluster ingress operator

          • 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.
          • To Do

          Spike - Represents a research-related task. NE-1034 Confirm Istio Gateway installation is possible "without sidecars enabled"

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

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: