Kong
Kong ships a Kubernetes ingress controller implementation which translates Ingress resources into Kong configuration. In this configuration a Kong cluster is created within the cluster.
Installation
Installation is either via Kubernetes manifests or a Helm chart (kong
, in https://charts.konghq.com
).
Configuration
Kong's configuration is managed by the Kong operator, which monitors the various CRDs:
KongIngress
is an extension resource that stores Kong-specific configuration, associated with either anIngress
orService
resource:- When associated with an
Ingress
all routes associated with theIngress
resource are updated using eachKongIngress.route
. - When associated with a
Service
all services and upstreams in Kong are updated using eachKongIngress.proxy
andKongIngress.upstream
.
- When associated with an
KongPlugin
resources configure plugins againstIngress
,Service
, andKongConsumer
resources. They're namespace scoped.KongClusterPlugin
is a non-namespacedKongPlugin
.KongConsumer
configures Kong consumers.TCPIngress
allows exposing non-HTTP and non-gRPC services.KongCredential
is deprecated in favour ofSecret
.