FAQ

Managing Kong Konnect entities with Kong Gateway Operator is a feature that is under active development. This document addresses commonly asked questions.

I’m a Kong Ingress Controller user, how much will I have to learn?

Kong Gateway Operator uses the same custom resources as Kong Ingress Controller. A KongConsumer is the same no matter which product you’re using.

By default, all Kong* custom resources will be reconciled by Kong Ingress Controller. To make Kong Gateway Operator reconcile them with Konnect, you must provide a spec.controlPlaneRef.type of konnectNamespacedRef.

Can I use HTTPRoute and Ingress definitions?

For the first release, we have chosen to keep a 1:1 mapping between custom resources and Konnect entities. This means that you should create KongService and KongRoute resources rather than HTTPRoute or Ingress resources.

Support for standard Kubernetes resources is planned for the future.

How often does the reconcile loop run?

New resources are created immediately using the Konnect API.

Existing resources are processed once per minute by default. This is customizable, but we recommend keeping the default value so that you do not hit the Konnect API rate limit.

For more information, see how it works.

I deleted a resource in the UI, but it wasn’t recreated by the operator. Why?

Wait 60 seconds, then check the UI again. The reconcile loop only runs once per minute.

Can I use Secrets for consumer credentials like in Kong Ingress Controller?

Kong Gateway Operator uses new Credential CRDs for managing consumer credentials. We plan to support Kubernetes Secret resources in a future release. #618.

Can I adopt existing Konnect entities?

Adopting existing entities is planned, but not yet available. Only resources created by the operator can be managed using CRDs at this time. #460

How do I create a global plugin?

It is not yet possible to create a global plugin. This is due to Konnect resources being namespaced in Kong Gateway Operator, while global plugins are cluster scoped. We are investigating options in #440