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

Spike: Gateway API and Kuadrant Testing

    • Icon: Spike Spike
    • Resolution: Unresolved
    • Icon: Critical Critical
    • None
    • None
    • None
    • 0.000
    • 0
    • 0

      We provide Gateway API support with the Cluster Ingress Operator (CIO) which covers all the features within the standard. Kuadrant adds a ton of additional feature support on top of Gateway API which cover use cases not always covered by the standard.

      The purpose of this task is to assess anything that needs to be done to ensure clean interoperability of our deployment of OpenShift Service Mesh (OSSM) that the CIO utilizes for Gateway API with Kuadrant, and potentially any testing we should add to the CIO to ensure this compatibility over time. One initial iteration on this that might be reasonable would be some simple smoke tests. We anticipate a need for testing on both sides eventually, to ensure one side doesn't break the other.

      Prerequisite: https://github.com/Kuadrant/kuadrant-operator/issues/1200

            [NE-1967] Spike: Gateway API and Kuadrant Testing

            Note that even though this spike is now under the "Post GA tasks" epic, we still intend to do this spike prior to GA.

            Miciah Masters added a comment - Note that even though this spike is now under the "Post GA tasks" epic, we still intend to do this spike prior to GA.

              Unassigned Unassigned
              rh-ee-sutt Shane Utt
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: