Gateway Discovery

Gateway Discovery is a deployment topology in which Kong Ingress Controller and Kong Gateway are separate deployments in the Kubernetes cluster. Kong Ingress Controller uses Kubernetes service discovery to discover the Kong Gateway Pods.

It allows you to manage many Kong Gateway instances with one Kong Ingress Controller, providing lower resource usage compared to Sidecar deployments.

You don’t need to configure this manually due to the default value of gatewayDiscovery.generateAdminApiService=true in the Helm chart. The following information is for educational purposes only.

When Kong Ingress Controller starts running it looks for services that match the name in the --kong-admin-svc flag. This value is controlled by the gatewayDiscovery.adminApiService.namespace and gatewayDiscovery.adminApiService.name values in the Helm chart. Once the service is found, Kong Ingress Controller fetches a list of EndpointSlices containing all Kong Gateway instances.

Kong Ingress Controller proceeds to send configuration to all detected Kong Gateway instances using the POST /config endpoint on each running Data Plane. Once the Data Plane has loaded configuration, it is marked as ready and can start proxying traffic.

 
flowchart LR

A[ API Server]
KIC1[ KIC 
(Active)]
KIC2[ KIC
(Standby)]
KIC3[ KIC
(Standby)]
DP1[ Data Plane]
DP2[ Data Plane]
DP3[ Data Plane]
DP4[ Data Plane]

A-.KIC watches 
API server.- KIC1

subgraph B["Deployment with
leader election"]
subgraph C[" "]
  KIC1
end
  KIC2
  KIC3
end

KIC1 ----> DP1 & DP2 & DP3 & DP4

style B stroke-dasharray: 5 5
style C stroke:none,fill:none

  

Figure 1: In a Gateway discovery deployment, one active Kong Ingress Controller instance sends configuration to many Kong Gateways, which are scaled independently. Multiple KIC instances can be run for high availability requirements.