Using NGINX as public ingress and Kong for internal API Gateways


I wanted to bounce off one idea before we actually start coding. We want to build a multi-tenant k8s cluster (a tenant per product - all separated via namespaces) and the idea is to use NGINX as public ingress controller and we want to leave flexibility to the product team to choose API Gateway, and for now, we are starting with Kong.

I wanted to check is this direction possible with Kong? If yes, maybe a few pointers would be helpful.

Just from reading, it seems like it is possible. Kong needs to be installed as “ClusterIP” and ingress rule (ingress.class=nginx) needs to point to Kong Proxy which will then use it’s own routing rules from there.

© 2019 Kong Inc.    Terms  •  Privacy  •  FAQ