The article explores various Kubernetes deployment strategies for Kong, focusing on configurations with and without databases and the role of the Kong Ingress Controller in simplifying API exposure on Kubernetes. It highlights the dominance of Kubernetes in container orchestration and discusses the benefits of deploying Kong on Kubernetes, including ease of scaling and flexibility in using databases either within or outside the cluster. The Kong Ingress Controller, which can operate in DB-less mode, allows developers to manage configurations using Kubernetes resources, reducing the need for multiple repositories. The piece further examines scaling strategies, such as running multiple Kong instances, and the introduction of control plane and data plane separation to leverage database features. It also addresses deployments involving multiple Kong Ingress Controllers for namespace isolation and discusses the potential for enhanced reliability through horizontal scaling. The article concludes by suggesting future discussions on resilient architectures and distributed deployments across multiple regions.