News for hackers. Stuff that matters.
Re:Comparison of Kubernetes Ingress Controllers by sandGorgon on Thursday October 22, 2020 @12:18PM (#24859688)
This is excellent. One thing is missing - support for Proxy Protocol.

It is the only real, standards compliant way in which you can preserve client information (IP address, etc) while its moving inside a kubernetes cluster. Not all ingresses have support for injecting it. Most ingresses can read it (assuming a cloud based load balancer has inserted it already).

We had moved to haproxy for this reason.

Re:Comparison of Kubernetes Ingress Controllers by stedaniels on Thursday October 22, 2020 @04:05PM (#24862727)
If you don't need the client IP for the application to work, but would like it for logging, consider community-id: https://github.com/corelight/community-id-spec
Re:Comparison of Kubernetes Ingress Controllers by Fumtumi on Thursday October 22, 2020 @12:46PM (#24860061)
Huh? I don't think i get this.

Is Proxy Protocol different to making sure to add client information as an extra header?

At least thats what we normally do, we make sure that client information like the client ip are added as header filds which can easily be used in monitoring and co.

Re:Comparison of Kubernetes Ingress Controllers by deathanatos on Thursday October 22, 2020 @01:04PM (#24860292)
I think they're referring to this protocol: http://www.haproxy.org/download/1.8/doc/proxy-protocol.txt

It wraps a TCP connection (not just HTTP) and forwards it, and preserves the originating IP information as a small header on the proxied connection.

It's supported beyond HAProxy, too; e.g., AWS ELBs support it. I've used it when forwarding TLS connections, but not wanting to lose the remote IP information. (And not wanting to decrypt on the ELB, which is required to add, e.g., an HTTP Forwarded-For header.)

Re:Comparison of Kubernetes Ingress Controllers by sandGorgon on Thursday October 22, 2020 @02:15PM (#24861280)
Your header is your custom way .

If you add your header and the next hop is to apache or some other software (for e.g.), it won't know what you did.

Proxy protocol is a standard. Every software that supports proxy protocol reads and write it in the same way. This is supported outside of software. All clouds (AWS, GCP, Azure ) support it. So does third party services like Cloudflare - https://developers.cloudflare.com/spectrum/proxy-protocol

Re:Comparison of Kubernetes Ingress Controllers by 0xEFF on Thursday October 22, 2020 @01:30PM (#24860623)
Different software expects different headers for http, and some software isn’t http based. Proxy protocol addresses these situations.