-
Notifications
You must be signed in to change notification settings - Fork 34
Add Proxy Protocol Support #49
Comments
Maybe need to look more closely at AWS deployment options. I think the operator should deal with low-level stuff like what annotations to make and the user should specify some sort of high-level AWS-specific goals. |
xref: #70 |
I think switching over to NLBs is fine, but we're not an |
AFAIK the other major platforms provide source preservation. At least Azure and GCP do. AWS's ELBs are the odd one out here. |
Right. This was what the kustomize PR #2474 did. Pretty sure that NLB works out cheaper https://aws.amazon.com/elasticloadbalancing/pricing/ |
xref contour nlb docs: https://projectcontour.io/guides/deploy-aws-nlb/ |
xref contour proxy protocol support docs: https://projectcontour.io/guides/proxy-proto/ |
Please describe the problem you have
Currently, the Envoy
Service
is annotated with "service.beta.kubernetes.io/aws-load-balancer-backend-protocol: tcp" that places the AWS ELB in TCP mode. This causes the ELB to masquerade the client IP. Adding proxy protocol support will allow the client IP to be preserved for ELB'd connections.Another approach is to use AWS NLB instead of ELB since NLB natively preserves client IPs.
/cc @jpeach @stevesloka @michmike
xref: examples/contour/02-service-envoy
The text was updated successfully, but these errors were encountered: