White list IP restriction nor working anymore

We are using kong with ingress in production and it is deploy with helm chart

  • kong : 1.3
  • Ingress Controller : 0.6.0

We use to deploy via https://bit.ly/k4k8s and we managed to configure IP restrcition.

The only difference is that we used our own database (google cloud SQL) to store the data.

Unfortunetly it is not the case anymore, we try a simple whilte list Ip restriction to protect some of our services but all the request are block for every Ip including the one in the whitelist group

apiVersion: configuration.konghq.com/v1
kind: KongPlugin
  name: white-list-intra
  namespace : A
plugin: ip-restriction

then we patched the ingress

apiVersion: extensions/v1beta1
kind: Ingress
   kubernetes.io/ingress.class: "kong"
   nginx.ingress.kubernetes.io/use-regex: "true"
   certmanager.k8s.io/cluster-issuer: letsencrypt-production-issuer
   plugins.konghq.com: white-list-intra
 name: ingress-A
 namespace: default

Are we doing something wrong or is it a bug? Could it come from the google cloud sql kong database ?

You should make sure that Kong is actually seeing the public IP address of the end-user which is making the request to Kong.
It is likely that you have a load-balancer in front of Kong and that is hiding the IP-address of the real request.
You need to check Kong’s trusted_ips setting and also check if you need to enable proxy_protocol or not. These will depend on the cloud provider you’re using.

Thanks for your answer, so it is link with this topic ? I will try to set thoses parameters.

We are running our k8s cluster on the google cloud platform, I thought that by using kong as our main loadbalancer we did not used the google one’s anymore ? What other google services can hide the IP from kong ?

Any advice on running kong in gcp in order to enable IP restriction ?

I have expose a simple API that show me the header that come in http request, and I see than when I put the api behind kong, the X-Forwarded-For and the X-Forwarded-For header don’t point to my IP but an other one ( I am trying to determine it sources).

The ip-restriction plugin look at the X-real-IP isn’t it ?So I have to config kong so that I have the good value in this header ?

It most likely is the LoadBalancer IP address that Kong is seeing.

As I said in my previous comment, you want to set trusted_ips setting in Kong so that Kong respects the correct IP address that is forward from Google’s Load Balancer (if you are using L7 LB form Google).

You can also set the traffic policy in GKE to preserve the client IP address:

I finaly found the solution, I simply add :

  externalTrafficPolicy: Local

to my values.yaml (for helm installation) It was previously set to Cluster: and the client IP was not forwarding correctly.