Kong Ingress Controller for Kubernetes Association
This feature is released as beta and should not be deployed in a production environment.
You can use native Kubernetes resources to configure your clusters in Konnect by associating your Kong Ingress Controller (KIC) for Kubernetes deployment with Konnect. This setup is ideal for organizations who want to manage gateways in Konnect through native Kubernetes resources without having to use a hybrid deployment model.
Note: KIC in Konnect is available to existing Enterprise-tier customers, and Kong is extending support to new signups for Free and Plus tiers.
About KIC in Konnect
Kong Ingress Controller (KIC) for Kubernetes configures Kong Gateway using Ingress or Gateway API resources created inside a Kubernetes cluster.
Beyond proxying the traffic coming into a Kubernetes cluster, KIC also lets you configure plugins, load balancing, health checking, and leverage all that Kong Gateway offers in a standalone installation. For more information about KIC, see Kong Ingress Controller Design.
By associating your KIC deployment with Konnect, this read-only association allows you to view your runtime entities, such as routes and applications, from your Kubernetes resources in Konnect.
Here are a few benefits of running KIC in Konnect over a self-managed setup:
- Easy to set up: The wizard allows you to add your KIC runtime group to Konnect in minutes.
- Centralized API management: KIC in Konnect allows organizations to have a centralized platform for API management, regardless of your individual teams’ choice of API management, whether that is using Kubernetes or Konnect.
KIC in Konnect association
To associate your KIC runtime instances with Konnect, use the setup wizard to add your KIC deployment to a KIC runtime group.
In Konnect, navigate to Runtime Manager, then click New Runtime Group > Kubernetes Ingress Controller.
Note: KIC OSS users can connect to Konnect’s Free tier, while KIC Enterprise users can connect to Konnect’s Enterprise tier.
If you don’t have an existing KIC deployment, you need the following before using the instructions in the wizard:
- A Kubernetes cluster
oc(if you’re working with OpenShift) installed and configured to communicate with your Kubernetes TLS
- Helm 3 installed
View KIC entities
After your KIC deployment is connected to Konnect, you can view the details for each runtime instance in your KIC runtime groups.
Figure 1: This image shows a KIC runtime instance dashboard. For each KIC runtime instance, you can see details about the runtime instance, analytics, and KIC status details.
Note: The KIC deployment in Konnect is currently read-only. The configuration of the gateway runtime is controlled by changes to resources in the Kubernetes API, and reflected here. For more information about how to manage these resources in KIC, see Custom Resources.
- Kong Ingress Controller Deployment Learn about the various deployment methods for KIC.
- Getting started with the Kong Ingress Controller This guide walks through setting up an HTTP(S) route and plugin using Kong Gateway and KIC.
- Analyze Services and Routes Learn how to use monitoring tools in Konnect to analyze KIC entities.
- Publish and Consume Services Find out how to publish services to the Dev Portal.