Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Gateway Core Support #612

Closed
10 tasks done
mpstefan opened this issue May 3, 2023 · 0 comments
Closed
10 tasks done

Gateway Core Support #612

mpstefan opened this issue May 3, 2023 · 0 comments
Labels
enhancement New feature or request epic Represents an epic. Contains sub-issues refined Requirements are refined and the issue is ready to be implemented.
Milestone

Comments

@mpstefan
Copy link
Collaborator

mpstefan commented May 3, 2023

For our release of NGINX Gateway v1.0, we need at least core support for the Gateway API Object 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".

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

  • listener tls options
  • requested addresses

Acceptance:

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

Stories

Preview Give feedback
  1. area/gateway/core enhancement refined
    sjberman
  2. area/gateway/core conformance enhancement refined
    sjberman
  3. area/nginx-configuration bug refined
    ciarams87
  4. area/gateway/core conformance enhancement refined
    kate-osborn
  5. area/gateway/core conformance enhancement refined
    sjberman
  6. area/control-plane enhancement refined
    pleshakov
  7. area/httproute/core enhancement refined
    sjberman
  8. blocked documentation refined
    kate-osborn
  9. area/gateway/core enhancement refined
    sjberman
  10. area/gateway/core enhancement refined
    ciarams87

For Discussion:

  • Why would a listener be able to accept TCP, TLS, and UDP traffic without having the matching route? How do the Gateway conformance tests test for this?
    • The Kubernetes API specification for ProtocolType mentions implementations are not required to accept all the defined protocols, yet lists HTTP, HTTPS, TCP, TLS, and UDP as "core".
  • Will Secrets be sufficient to store listener tls certificateRefs for core? The specification states:
    A single CertificateRef to a Kubernetes Secret has \"Core\" support. Implementations MAY choose to support attaching multiple certificates to a Listener, but this behavior is implementation-specific.
    Any additional detail around "partial support" for certificateRefs?
  • GatewayStatus does not specify a support level. Is GatewayStatus included in the conformance tests? How necessary is its inclusion in our v1.0?
@mpstefan mpstefan converted this from a draft issue May 3, 2023
@mpstefan mpstefan added this to the v0.5.0 milestone May 3, 2023
@mpstefan mpstefan added the epic Represents an epic. Contains sub-issues label May 3, 2023
@mpstefan mpstefan added the refined Requirements are refined and the issue is ready to be implemented. label May 30, 2023
@mpstefan mpstefan moved this from 🆕 New to 🏗 In Progress in NGINX Gateway Fabric May 31, 2023
@mpstefan mpstefan added the enhancement New feature or request label Jun 9, 2023
@mpstefan mpstefan moved this from 🏗 In Progress to ✅ Done in NGINX Gateway Fabric Jul 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request epic Represents an epic. Contains sub-issues refined Requirements are refined and the issue is ready to be implemented.
Projects
Archived in project
Development

No branches or pull requests

1 participant