Installing Kong Ingress Controller (KIC)

In this article, we will move from theory to a real deployment. The goal is to install Kong Ingress Controller (KIC) in a Kubernetes cluster, verify that Kong Gateway is working properly, and prepare the external exposure of the proxy so that we can publish applications from the cluster itself. To keep the lab simple, I will use a single virtual machine created with Vagrant on which I will run a k3s cluster. This choice does not change the way Kong works, but it allows us to focus on what really matters: what KIC installs, why the proxy service initially appears in Pending, and how to solve that with MetalLB.