In this tutorial, we'll dive into the seamless integration of dynamic scaling and instance discovery with KIC 2.9!
Today’s release allows running the Ingress Controller and the Kong Gateway data planes separately in different pods.
This feature enables KIC to scale cost-effectively as it removes the overhead of running the KIC sidecar with every single Gateway instance. Besides memory savings, users should also see a significant decrease in CPU usage.

@ViktorGamov a principal developer advocate at Kong, will guide you through a new feature.

Read more details in the official announcement blog https://konghq.com/blog/kong-ingress-controller-2-9