-
Notifications
You must be signed in to change notification settings - Fork 141
Closed
Labels
enhancementNew feature or requestNew feature or requestepicRepresents an epic. Contains sub-issuesRepresents an epic. Contains sub-issuesrefinedRequirements are refined and the issue is ready to be implemented.Requirements are refined and the issue is ready to be implemented.
Milestone
Description
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
requestRedirectpathresponseHeaderModifier,requestMirror,urlRewrite, andextensionReffilters.backendReffilters
Acceptance:
- Documentation is updated to reflect what extended features are still unsupported.
### Core Support Stories
- [ ] #479
- [ ] #478
- [ ] #476
- [ ] #480
- [ ] #606
- [ ] https://github.com/nginxinc/nginx-kubernetes-gateway/issues/611
- [ ] https://github.com/nginxinc/nginx-kubernetes-gateway/issues/306
- [ ] https://github.com/nginxinc/nginx-kubernetes-gateway/issues/687
- [ ] https://github.com/nginxinc/nginx-kubernetes-gateway/issues/755
- [ ] https://github.com/nginxinc/nginx-kubernetes-gateway/issues/776
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.
Metadata
Metadata
Assignees
Labels
enhancementNew feature or requestNew feature or requestepicRepresents an epic. Contains sub-issuesRepresents an epic. Contains sub-issuesrefinedRequirements are refined and the issue is ready to be implemented.Requirements are refined and the issue is ready to be implemented.