HTTP Route Core Support

[mpstefan]

For our release of NGINX Gateway v1.0, we need at least core support for HTTP Route as defined in the Kubernetes Gateway API v1beta1. This epic will track all the enhancements that need to be made to the HTTPRoute to reach support for "core".

Current Gateway compatibility doc

List of extended or implementation-specific features that will NOT be implemented at this time:

• Regular expression matching
• requestRedirect path
• responseHeaderModifier, requestMirror, urlRewrite, and extensionRef filters.
• backendRef filters

Acceptance:

• Documentation is updated to reflect what extended features are still unsupported.

Core Support Stories

Preview Give feedback

1. Core API: Support empty SectionName in HTTPRoute ParentRef nginx-kubernetes-gateway#479
   area/httproute/core enhancement refined +3
   
2. Route and Listener wildcard hostnames nginx-kubernetes-gateway#478
   area/httproute/core enhancement refined +3
   
3. Core API: Exact PathMatch nginx-kubernetes-gateway#476
   area/httproute/core enhancement refined +3
   
4. Core API: RequestHeaderModifier nginx-kubernetes-gateway#480
   area/httproute/core enhancement refined +3
   
5. Support zero hostnames in HTTPRoute nginx-kubernetes-gateway#606
   area/httproute/core bug conformance refined +4
   
6. Set ResolvedRef Condition to True in HTTPRoute status when all references are resolved nginx-kubernetes-gateway#611
   area/httproute/core conformance enhancement refined +4
   
7. Core API: Report proper conditions for HTTPRoute attachment edge cases nginx-kubernetes-gateway#306
   area/httproute/core enhancement refined +3
   
8. Update conformance documentation based on outcome of conformance tests nginx-kubernetes-gateway#687
   blocked documentation refined +3
   
9. Incorrect matching precedence order nginx-kubernetes-gateway#755
   area/httproute/core bug refined +3
   
10. Set ResolvedRefs/False/InvalidKind for BackendRefs with unknown kind nginx-kubernetes-gateway#776
    area/httproute/core bug refined +3
    

For Discussion:

• The spec appears to require regular expressions as an enum, but list the feature as "implementation-specific" - is this correct?
  • Yes
• What additional condition support do we need for status?
  • In theory, just ResolvedRefs. Conformance test will prompt additional functionality needed.
• What additional stories are needed for conformance? Previous list here: https://github.com/nginxinc/nginx-kubernetes-gateway/issues?q=is%3Aopen+is%3Aissue+label%3Aarea%2Fhttproute%2Fcore
  • Need to watch HTTPRoute partial validity #485 if it is merged.

[laotoutou]

Hi, The edge version doesn't implement URLRewrite yet, does it?

[mpstefan]

Hey @laotoutou, it does not. As URLRewrites are listed as an extended feature of the Gateway API at the moment, we have not prioritized them above any core features. I do not believe we will be getting to them in the near future, as Gateway 1.0 will be dropping soon as well, but you are always welcome to submit a discussion on the topic explaining why it's needed for your use case.

Happy to prioritize if others are also in need!

[winggundamth]

I'm not sure what the status of URLRewrite is right now. Does anyone have a workaround if I want to rewrite the URL?

[pleshakov]

@winggundamth please see #534 (comment)