<p>I am running Traefik on Kubernetes and I have create an Ingress with the following configuration: </p>

<pre><code>---
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: whitelist-ingress
  annotations:
    kubernetes.io/ingress.class: traefik
    traefik.frontend.rule.type: PathPrefix
    traefik.ingress.kubernetes.io/whitelist-source-range: "10.10.10.10/32, 10.10.2.10/23"
    ingress.kubernetes.io/whitelist-x-forwarded-for: "true"
    traefik.ingress.kubernetes.io/preserve-host: "true"
spec:
  rules:
  - host:
    http:
      paths:
      - path: /endpoint
        backend:
          serviceName: endpoint-service
          servicePort: endpoint-port
---
</code></pre>

<p>When I do a POST on the above endpoint, Traefik logs that the incoming IP is 172.16.0.1 and so my whitelist is not triggered. 
Doing an ifconfig I see that IP belongs to Docker </p>

<pre><code>docker0: flags=4099&lt;UP,BROADCAST,MULTICAST&gt;  mtu 1500
        inet 172.26.0.1  netmask 255.255.0.0  broadcast 172.26.255.255
</code></pre>

<p>How can I keep the original IP instead of the docker one? </p>

<p>EDIT</p>

<p>Traefik is exposed as LoadBalancer and the port is 443 over SSL</p>

<p>This is its yml configuration</p>

<pre><code>---
kind: Service
apiVersion: v1
metadata:
  name: traefik
  annotations: {}
    # service.beta.kubernetes.io/aws-load-balancer-internal: 0.0.0.0/0
spec:
  selector:
    k8s-app: traefik-ingress
  ports:
  - protocol: TCP
    port: 80
    targetPort: 80
    name: http
  - protocol: TCP
    port: 443
    targetPort: 443
    name: https
  type: LoadBalancer
  externalTrafficPolicy: Local
  externalIPs:
  - &lt;machine-ip&gt;
---

kind: Deployment
apiVersion: apps/v1
metadata:
  name: traefik-ingress-controller
  namespace: default
  labels:
    k8s-app: traefik-ingress
spec:
  replicas: 2
  selector:
    matchLabels:
      k8s-app: traefik-ingress
  template:
    metadata:
      labels:
        k8s-app: traefik-ingress
        name: traefik-ingress
    spec:
      hostNetwork: true
      serviceAccountName: traefik-ingress-controller
      terminationGracePeriodSeconds: 35
      volumes:
        - name: proxy-certs
          secret:
            secretName: proxy-certs
        - name: traefik-configmap
          configMap:
            name: traefik-configmap
      containers:
      - image: traefik:1.7.6
        name: traefik-ingress
        imagePullPolicy: IfNotPresent
        resources:
          limits:
            cpu: 200m
            memory: 900Mi
          requests:
            cpu: 25m
            memory: 512Mi
        livenessProbe:
          failureThreshold: 2
          httpGet:
            path: /ping
            port: 80
            scheme: HTTP
          initialDelaySeconds: 10
          periodSeconds: 5
        readinessProbe:
          failureThreshold: 2
          httpGet:
            path: /ping
            port: 80
            scheme: HTTP
          periodSeconds: 5
        volumeMounts:
          - mountPath: "/ssl"
            name: "proxy-certs"
          - mountPath: "/config"
            name: "traefik-configmap"
        ports:
        - name: http
          containerPort: 80
        - name: https
          containerPort: 443
        - name: dashboard
          containerPort: 8080
        args:
        - --logLevel=DEBUG
        - --configfile=/config/traefik.toml
---
</code></pre>

<p>As you can see here is the output of kubectl get svc </p>

<pre><code>traefik                       LoadBalancer   10.100.116.42    &lt;machine-ip&gt;     80:30222/TCP,443:31578/TCP   &lt;days-up&gt;
</code></pre>

<p>Note that Traefik is running in a single node kubernetes cluster (master/worker on the same node). </p>

Justin
<p>In LoadBalancer service type doc <a href="https://kubernetes.io/docs/concepts/services-networking/#ssl-support-on-aws" rel="nofollow noreferrer">ssl support on aws</a> you can read the following statement:</p>

<blockquote>
  <p>HTTP and HTTPS will select layer 7 proxying: the ELB will terminate
  the connection with the user, parse headers and inject the
  X-Forwarded-For header with the user’s IP address (pods will only see
  the IP address of the ELB at the other end of its connection) when
  forwarding requests.</p>
</blockquote>

<p>So if you add the following annotation to you traeffik service:</p>

<pre><code>service.beta.kubernetes.io/aws-load-balancer-backend-protocol: https
</code></pre>

<p>It should work with the <code>ingress.kubernetes.io/whitelist-x-forwarded-for: "true"</code> annotation present in your ingress config and the forwarded header is added by the aws loadbalancer.</p>

<p>Disclaimer: I have not tested that solution.</p>

<p>Regards.</p>
