These days I’m using the open source version of haproxy as ingress controller for Kubernetes over other popular options like Nginx and Traefik. haproxy is typically faster, and fixes for me a problem I had with Nginx: whenever Nginx reloads its configuration (for example, when my app creates an ingress resource for a custom domain), it cuts web sockets connections. Both Traefik and haproxy have a more dynamic reconfiguration so that problem doesn’t occur with either of these other ingress controllers. I prefer haproxy because of the performance and because I had some problems with Traefik when installed with the official Helm chart - it installs an older version of Traefik, among other things.
One issue I had with haproxy was that since I am using Cloudflare, all the IPs logged in haproxy’s access logs were Cloudflare’s IPs, instead the actual IPs of the users. Cloudflare sends the real IP with a CF-Connecting-IP header with each request, so we can use that header in our apps to identify the user’s IP correctly. We can easily do that with haproxy as well, so to fix the IPs shown in the access logs.
The first step is to create a config map in the namespace of the ingress controller, that includes the IPv4 and IPv6 ranges used by Cloudflare, which you can find here:
apiVersion: v1 data: cf-ips: |- 184.108.40.206/20 220.127.116.11/22 18.104.22.168/22 22.214.171.124/22 126.96.36.199/18 188.8.131.52/18 184.108.40.206/20 220.127.116.11/20 18.104.22.168/22 22.214.171.124/17 126.96.36.199/15 188.8.131.52/12 184.108.40.206/13 220.127.116.11/22 2400:cb00::/32 2606:4700::/32 2803:f800::/32 2405:b500::/32 2405:8100::/32 2a06:98c0::/29 2c0f:f248::/32 kind: ConfigMap metadata: name: cf-ips namespace: haproxy-ingress
I’ve installed haproxy in the haproxy-ingress namespace, so if you have installed it in a different namespace make sure to change that in the YAML manifest.
Next, you need to edit the haproxy deployment and mount that config map to a path in the controller’s container:
spec: template: spec: containers: - image: quay.io/jcmoraisjr/haproxy-ingress:v0.7.2 name: haproxy-ingress volumeMounts: - mountPath: /etc/haproxy/cf-ips name: cf-ips volumes: - configMap: defaultMode: 256 items: - key: cf-ips path: cf-ips name: cf-ips optional: false name: cf-ips
The final step is to add a simple annotation to each ingress resource that instructs haproxy to get the real IP from the CF-Connecting-IP header if the request originates from Cloudflare:
annotations: ingress.kubernetes.io/config-backend: | acl from_cf src -f /etc/haproxy/cf-ips/cf-ips http-request set-src req.hdr(CF-Connecting-IP) if from_cf
That’s it! It’s very simple and fixes an annoying issue. Hope it helps.
I am a passionate web developer based in Espoo, Finland. I am the founder and developer of www.dynablogger.com, a new blogging platform. Besides computing, I love boxing, martial arts, and good food!