Kong Ingress Controller can be deployed in many different topologies depending on your needs. The primary methods to deploy Kong Ingress Controller are:
Gateway Discovery - The recommended method to deploy Kong Ingress Controller.
Database Backed with Gateway Discovery - Gateway Discovery with an additional Lua control plane and Postgres database.
Traditional (Sidecar) - Run Kong Ingress Controller as a sidecar container in the same Pod as Kong Gateway (legacy deployment).
If you’re starting a greenfield project today we recommend using Gateway Discovery. If you’re a long-time user of Kong Ingress Controller you’re likely to be using the sidecar model. This approach is still valid and supported, but is not as resource efficient as Gateway Discovery.