You are browsing documentation for an outdated version.
See the latest documentation here.
Both Kong Gateway Operator and Kong Ingress Controller can be configured using the Kubernetes Gateway API. Configure your vendor independent
Gateway objects and Kong Gateway Operator translates those requirements in to Kong specific configuration.
In DB-less mode, Kong Gateway Operator watches for
GatewayClass resources where the
konghq.com/gateway-operator. When a
GatewayClass resource is detected, Kong Gateway Operator deploys an instance of Kong Ingress Controller to act as a
ControlPlane and an instance of Kong Gateway to act a
Configure traffic routing using Gateway API resources such as
UDPRoute. These resources are translated in to Kong configuration objects by Kong Ingress Controller which proxies traffic to your internal services through Kong Gateway .