Kong Gateway traffic control and routing

Kong Gateway has several default ports it uses to listen to traffic.

Defines a list of addresses/ports on which Kong Gateway will accept public HTTP (gRPC, WebSocket, etc) traffic from clients and proxy it to your upstream services (8000 by default).

Defines a list of addresses and ports, but those should be restricted to only be accessed by administrators, as they expose Kong Gateway’s configuration capabilities via the Admin API.

Similar to proxy_listen, but for Layer 4 (TCP, TLS) generic proxy. This is disabled by default.

Routes determine how requests are sent to their Services after they reach Kong Gateway.

The expressions router provides a Domain Specific Language (DSL) that allows for complex routing rule definitions.

A Kong Gateway routing configuration format. It uses JSON to provide a list of routing criteria.

Kong Gateway implements load balancing capabilities to distribute proxied requests across a pool of instances of an upstream service.

Plugins can execute during several phases of the request lifecycle.

Once Kong Gateway has executed all the necessary logic (including plugins), it is ready to forward the request to your upstream service.

Kong Gateway receives the response from the upstream service and sends it back to the downstream client in a streaming fashion.

Slowly roll out software changes to a subset of users

Consume messages from Confluent Cloud Kafka topics and make them available through HTTP endpoints