You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So for 443/80 ports I need proxy protocol and it works as expected, but for port 22 I don't need it. If I disabled it in target group by hands aws-load-balancer-controler sets proxy protocol for that tcp 22 port back after some time.
I know it is also possible to set something like this fornginx-ingress:
@wweiwei-li What would be the ideal way to implement this? Would a target group override annotation for the service port be reasonable? for example below this would disable proxy_protocol_v2 for port 443.
I'm using nginx-ingress and want to expose gitlab-shell service on TCP port 22.
So for 443/80 ports I need proxy protocol and it works as expected, but for port 22 I don't need it. If I disabled it in target group by hands aws-load-balancer-controler sets proxy protocol for that tcp 22 port back after some time.
I know it is also possible to set something like this fornginx-ingress:
But none of them works.
Describe the solution you'd like
Ability to disable proxy-protocol for specific ports.
Describe alternatives you've considered
Using https://kubernetes-sigs.github.io/aws-load-balancer-controller/v2.9/guide/targetgroupbinding/targetgroupbinding/ this maybe.
The text was updated successfully, but these errors were encountered: