Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add option to enable proxy protocol RE:#699 #1002

Closed
dcherniv opened this issue Jan 17, 2020 · 12 comments
Closed

Add option to enable proxy protocol RE:#699 #1002

dcherniv opened this issue Jan 17, 2020 · 12 comments
Assignees
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Comments

@dcherniv
Copy link

Please refer to #699
This is desperately needed for feature parity with AWS.

@nesl247
Copy link

nesl247 commented Mar 30, 2020

Any update?

@CapoD
Copy link

CapoD commented Mar 31, 2020

Currently, we are using GKE + Istio (automatically installed) and our applications need to know the source IP of a request.
Since Istio ingress-gateway service is configuring a TCP Load Balancer, we would need to enable the Proxy Protocol on the GCP LB. Unfortunately, this can only be done on creation.
So we would ask you to provide a service annotation that would allow us to set the Proxy Protocol (Version).
In AWS this can be done

@rramkumar1
Copy link
Contributor

@bowei Is this something that can be addressed by the Gateway API?

/assign @bowei

@bowei
Copy link
Member

bowei commented Apr 20, 2020

It seems to make more sense as a value for app-protocol, may want to xref on k/k

@unixfox
Copy link

unixfox commented Jun 26, 2020

I'm also interested into this new annotation. I would like to deploy NGINX behind a TCP LB and I need to preserve the original IP address of the clients.

@gustavovalverde
Copy link

For people trying to preserve the client's Source IP using Nginx, there's no need to use Proxy Protocol, installing with this configuration will do it (use an updated Nginx):

  config:
    enable-real-ip: "true"
    use-forwarded-headers: "true"
    proxy-real-ip-cidr: "130.211.0.0/22,35.191.0.0/[L7-LB_EXTERNAL_IP]/32"

cc: @unixfox

@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 15, 2020
@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Dec 15, 2020
@fejta-bot
Copy link

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

@k8s-ci-robot
Copy link
Contributor

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@nesl247
Copy link

nesl247 commented Jan 14, 2021

/reopen

@k8s-ci-robot
Copy link
Contributor

@nesl247: You can't reopen an issue/PR unless you authored it or you are a collaborator.

In response to this:

/reopen

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
None yet
Development

No branches or pull requests

9 participants