Last week, we announced the release of the Kong Ingress Controller for Kubernetes, a tool to help bridge the gap in deploying Kong onto Kubernetes, and ensure its full integration into the Cloud Native landscape of today.
Deploying Kong onto Kubernetes has always been an easy process, mostly thanks to Kong’s platform agnosticism. However, the integration of services managed by Kubernetes with Kong still used to remain a manual process and involve some extra integration effort. No more!
By integrating with the Kubernetes Ingress Controller specifications, Kong directly ties into the Kubernetes lifecycle, and as applications are deployed and new services created, Kong will automatically live-configure itself to serve traffic to these services:
This pattern, enabled by the Kong Ingress Controller, follows the Kubernetes philosophy of using declarative resources to define what we want to happen, rather than the historical imperative model of configuring servers how we want them to be.
The Kong Ingress Controller is open source, and ready to use and receive feedback and contributions:
If you have questions or comments about using the Kong Ingress Controller for Kubernetes, or using Kong on Kubernetes in general, don’t hesitate to ask in our new dedicated Kubernetes Category!