Skip to content

Add GEP-1713: ListenerSets - Standard Mechanism to Merge Multiple Gateways support #10662

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.

Sign up for GitHub

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

Jump to bottom
Open
5 tasks
DuncanDoyle opened this issue Feb 19, 2025 · 2 comments · May be fixed by #11255
Open
5 tasks

Add GEP-1713: ListenerSets - Standard Mechanism to Merge Multiple Gateways support #10662

DuncanDoyle opened this issue Feb 19, 2025 · 2 comments · May be fixed by #11255
Assignees
@davidjumani
Labels
control-plane-parity scope/1.19 Type: Enhancement New feature or request

Comments

@DuncanDoyle
Copy link
Collaborator

DuncanDoyle commented Feb 19, 2025 •
edited
Loading

kgateway version

1.19

Is your feature request related to a problem? Please describe.

GEP-1713: ListenerSets - Standard Mechanism to Merge Multiple Gateways introduces support for a concept called ListenerSets. This concept decouples the definition and configuration of Listeners from the Gateway CR.

This has a number of advantages:

  • The current limit of Listeners is 64, which means only 64 SNI domains can be configured. We have customers that have many more domains on a single gateway.
  • The Gloo Edge API allowed application teams to configure both the TLS Certs and SNI Domains as well as the routing logic in a single CR (VirtualService). With Gateway API, application teams can no longer own the configuration of Certs and SNI, as this needs to be configured in the Gateway CR (== platform team). ListenerSets would create the required decoupling to implement this separation of concern.

Describe the solution you'd like

Add support for ListenerSets as defined in GEP-1713: ListenerSets - Standard Mechanism to Merge Multiple Gateways](https://gateway-api.sigs.k8s.io/geps/gep-1713/).

Add the following support:

  • Create an enhancement proposal that provides the API design and implementation.
  • Add initial e2e tests for this feature.
  • Update CI to run e2e tests.
  • Add initial user docs.
  • TBD

Describe alternatives you've considered

Do not support the Gateway API Inference Extension project.

Additional Context
@DuncanDoyle DuncanDoyle added the Type: Enhancement New feature or request label Feb 19, 2025
stevenctl pushed a commit to stevenctl/gloo that referenced this issue Mar 12, 2025
@day0ops @sam-heilbron
Attach jwt failure status to metadata (kgateway-dev#10662)
a1a5d36 
Signed-off-by: day0ops <kasun.talwatta@gmail.com>
Co-authored-by: Sam Heilbron <SamHeilbron@gmail.com>
@davidjumani davidjumani self-assigned this Mar 20, 2025
@soloio-bot
Copy link

Zendesk ticket #4644 has been linked to this issue.

@davidjumani
Copy link
Contributor

This has been added in solo-io#10713 and can be ported over

@davidjumani davidjumani moved this from Backlog to In progress in Kgateway Planning May 20, 2025
@davidjumani davidjumani linked a pull request May 23, 2025 that will close this issue
Open
@davidjumani davidjumani moved this from In progress to In review in Kgateway Planning May 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@davidjumani davidjumani

Labels
control-plane-parity scope/1.19 Type: Enhancement New feature or request
Projects
Kgateway Planning
Status: In review
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add support for GEP-1713: ListenerSets davidjumani/kgateway
4 participants
@DuncanDoyle @lgadban @davidjumani @soloio-bot