Incorrect prefix path matching

[kate-osborn]

For the following HTTPRoute:

apiVersion: gateway.networking.k8s.io/v1beta1
kind: HTTPRoute
metadata:
  name: matching
  namespace: gateway-conformance-infra
spec:
  parentRefs:
  - name: same-namespace
  rules:
  - matches:
    - path:
        type: PathPrefix
        value: /
    - headers:
      - name: version
        value: one
    backendRefs:
    - name: infra-backend-v1
      port: 8080
  - matches:
    - path:
        type: PathPrefix
        value: /v2
    - headers:
      - name: version
        value: two
    backendRefs:
    - name: infra-backend-v2
      port: 8080

a request to /v2example must be routed to infra-backend-v1.

However, NKG routes the request to infra-backend-v2.

Acceptance Criteria:

• Make the conformance test HTTPRouteMatching pass. Note that only the v2example'_should_go_to_infra-backend-v1 test case fails.

[mpstefan]

This "bug" exists because NGINX does prefixes based on comparing the path strings. Gateway API requires that a / is present for a prefix.