Setup Kong Ingress Controller on AKS using existing IP address

Hi Kong Nation,

I have recently started looking at using Kong Ingress instead of NGINX on my AKS cluster. The problem I am facing is, when I create a new AKS cluster, it creates a loadbalancer + IP address and by creating Kong Ingress it creates another loadbalancer + IP address. Is there any way to instruct Kong Ingress to re-use the existing IP address instead of creating new one. (I was able to achieve the same on NGINX by using --set controller.service.loadBalancerIP=$PUBLICIP)

Cheers,

I found the answer :grinning:

Please share with me your answer to this problem. Thanks for the sharing.

Have you ever set proxy.externalTrafficPolicy=Local and proxy.loadBalancerIP=$StaticIP like code below yet

helm install kong/kong --generate-name \
    --namespace kong \
    --set ingressController.installCRDs=false \
    --set proxy.externalTrafficPolicy=Local \
    --set proxy.loadBalancerIP=$StaticIP

Let’s me know if it works