Gateway API Enhancement Proposal Tracker

[kate-osborn]

This discussion is to track the Gateway API Enhancement Proposals (GEPs) that NGF will need to implement.

Gateway API Project Board (Standard)
Gateway API Project Board (Experimental)

GEP	GEP Status	Notes	Status
Named Route Rules	Standard	N/A	To Do
Multiple Certs Per Listener	Standard	Issue	Done
HTTPRoute Retries	Experimental	NGINX may need a custom module to implement GEP. Issue	To Do
HTTPRoute Timeouts	Standard	NGINX will need a custom module to implement GEP. Issue	To Do
ListenerSets	Standard	N/A	Done
CORS Filter	Standard	N/A	Done
ExternalAuth Filter	Experimental	N/A	In Progress
Client Certificate Validation	Standard	N/A	Done
Session Persistence	Experimental	Cookie-based is NGINX Plus only; OSS uses ip_hash LB method	Done for HTTPRoute (no BackendLBPolicy support)
Backend mTLS	Standard	N/A	Done

[ryan-dyer-sp]

I believe ListenerSets went experimental with the recent 1.3.0 release of GatewayAPI.

[pawelpabich]

👋

Are there any plans to implement ListenerSets soon? Is that something you think the community could contribute? If so, would that be the case even for someone who hasn't contributed to the project before?

[sjberman]

Hi @pawelpabich, ListenerSets are on our roadmap for an upcoming release. We love when community members contribute, however we don't yet have an issue opened for supporting ListenerSets, so we'll need to do that and describe all of the necessary details before it's clear on how to implement it.

[pawelpabich]

I understand. Can you link to the issue in this thread once it's created? Thanks!

[sjberman]

#4376