Arko Dasgupta

we discussed this in the communtiy meeting last week, adding a field in `EnvoyGateway` config and populating that via helm is probably the way to go here

ptal @envoyproxy/gateway-maintainers @envoyproxy/gateway-reviewers

Its looks like we've had multiple users requesting `Daemonset` + `hostNetwork` mode `mode` may get tricky for 2 cases * we've already called it `envoyDeployment` * we want to add...

+1

go for it @NomadXD !

@NomadXD we need a `Name` to create a unique xds listener (in case none exist and `findXdsListenerByHostPort` returns `null`)

@envoyproxy/gateway-maintainers should the Xds Listener name be based off the IR Listener Name or the Listening Address and Port as suggested above ?

hey @NomadXD, @zirain @AliceProxy and I discussed this in the community meeting today and we prefer mapping the xds Listener name to the IR name to improve debuggability of mapping...

thanks @dboslee ! assigning this to you

> As discussed in today's meeting, I prefer to remove the `EnvoyGatewayCustomProvider` and add a flat `EnvoyGatewayFileProvider`(or a better name). Custom is needed to allow for different resource and infra...