Kong Ingress Controller automatically creates a kong
IngressClass
when installed. All of the example ingress definitions in the documentation set spec.ingressClassName: kong
, which allows things to work by default.
Advanced users of Kong Ingress Controller may want to split traffic into internal and external ingress definitions. This requires multiple Kong Ingress Controller instances, each pointing to a different IngressClass
.
You can also split traffic into different gateways when you are using Gateway APIs with multiple Kong Ingress Controller instances and multiple Gateway
s.