Epic - Listener Customization - IP & IPFamily #5363
Labels
backlog
Pull requests/issues that are backlog items
epic
Issues that need to be broken into smaller issues
ready for refinement
An issue that was triaged and it is ready to be refined
Milestone
Discussed in #3724
Originally posted by brianehlert April 4, 2023
Project users have asked for an easy way to deploy NIC with non-default and / or custom listeners for http (L7) as well as stream (L4). The stream use case is currently enabled through the GlobalConfiguration custom resource.
It is possible to modify the http listeners today, however the path for customers to do this is complicated and involves modifying the core listener template.
This has been requested for the use cases of:
Project users should not have to modify the project code or templates to set non-default listeners.
Suggested modification to GlobalConfiguration to help visualize:
https://github.com/nginxinc/kubernetes-ingress/blob/main/examples/custom-resources/basic-tcp-udp/global-configuration.yaml
The listener names would then be referenced following the current pattern in TransportServer
https://github.com/nginxinc/kubernetes-ingress/blob/main/examples/custom-resources/basic-tcp-udp/transport-server-tcp.yaml
This is necessary for many of these use cases because this all happens at the socket / session / listener level with NGINX.
The text was updated successfully, but these errors were encountered: