kubernetes-sigs
Make the maximum number of listeners in Gateway CRD configurable
What would you like to be added:
I would like the gateway CRD template to be improved by making the maxItems on the gateway listeners to be configurable instead of it being hard coded to be 64 items (see experimental gateway CRD).
Why this is needed: Our current setup uses an "edge" gateway (Kubernetes Gateway API gateway) routing requests to other "inner" gateways based on the path prefix. We currently have around 30 inner gateways which the edge gateway routes requests to, but we will have more in the future, so we will hit the hard coded limit of 64 max really soon.
There is a lot of discussion around similar topics in https://github.com/kubernetes-sigs/gateway-api/pull/1863.
IMO, I strongly agree with the need to have >64. But a few notes
- Just raising the limit is probably not sufficient, as realistically its not going to be so on the order of the largest users requirements (lets say 10k listeners)
- A more scalable approach is to split out the listeners, as the merging GEP above does
- Having different limits in different CRDs is probably a bad precedent to set; there should be 1 single API definition across users/clusters/implementations
cc @robscott
