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

[GWAPI-TP] E2E testing for Gateway API

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • None
    • E2E testing for Gateway API
    • 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
    • 26
    • 26% 26%
    • M
    • Sprint 234, Sprint 235, Sprint 236
    • 0
    • 0.0

      Continue work for E2E tests for the implementation of "gatewaycontroller" in https://issues.redhat.com/browse/NE-1206 

      Some ideas for the test include:

      1. Test installation: Create GatewayClass with spec.controllerName: openshift.io/gateway-controller and ensure the following:
        1. Istio Operator successfully gets installed
        2. The expected Gateway API CRDs are installed (done in NE-1208)
        3. The SMCP gets created
        4. Istiod control plane gets stood up
        5. Istio-ingressgateway exists and is healthy
      2. Automatic deployments work by creating a Gateway controller - Istio creates an envoy proxy for the gateway
      3. End-to-End Ingress Check: Create HTTPRoute, and attach to Gateway, ensure connectivity
      4. Ingress op creates the catalog source and subscription automatically for a Istio image that is publicly available

            cholman@redhat.com Candace Holman
            gspence@redhat.com Grant Spence
            Hongan Li Hongan Li
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: