Is your feature request related to a problem? Please describe.
A frontend listener and port can be defined however it's impossible (as far as I'm aware) to add the ,PROXY command to the listener which will instruct Varnish to listen for the PROXY protocol.
I'd like to be able to define a normal frontend i.e. the same as the existing Frontend host + port and to specify an additional listener with PROXY protocol enabled on a defined port.
This can be achieved by passing multiple -a directives to varnishd however this isn't possible using kube-httpcache:
varnishd -a 0.0.0.0:8080 -a 0.0.0.0:6081,PROXY
Describe the solution you'd like
The ability to add additional frontend host/port listeners and whether they use the PROXY protocol or not.
Is your feature request related to a problem? Please describe.
A frontend listener and port can be defined however it's impossible (as far as I'm aware) to add the
,PROXYcommand to the listener which will instruct Varnish to listen for thePROXYprotocol.I'd like to be able to define a normal frontend i.e. the same as the existing Frontend host + port and to specify an additional listener with PROXY protocol enabled on a defined port.
This can be achieved by passing multiple
-adirectives tovarnishdhowever this isn't possible usingkube-httpcache:varnishd -a 0.0.0.0:8080 -a 0.0.0.0:6081,PROXYDescribe the solution you'd like The ability to add additional frontend host/port listeners and whether they use the
PROXYprotocol or not.Describe alternatives you've considered N/A
Additional context N/A