Hi Kong Community,
We are currently looking at an API gateway for our organisation and have decided on Kong for a number of reasons. Before asking my question I want to give a brief overview of of our landscape, we are moving to a microservice architecture and a Kubernetes cluster will host these new services but we also have legacy services that need to be secured by a gateway as well.
With that in mind, from my understanding we’ll need an ingress controller to expose any services out side of Kubernetes which will mostly likely be Kong Ingress Controller. But if we want to control external services sitting outside of Kubernetes cluster then we’ll also need Kong API gateway to sit in front of these services.
Does Kong Ingress Controller have any egress functionality? i.e. Can the Kong ingress controller act as a fully fledged API gateway or does as the name suggests only handle ingress for Kubernetes?