FAQ

Managing Konnect entities with Kong Gateway Operator is an actively developed feature. This page answers frequently asked questions.

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.

Not yet. The initial release uses a 1:1 mapping between custom resources and Konnect entities. Use KongService and KongRoute instead of HTTPRoute or Ingress.

Support for standard Kubernetes resources is planned for the future.

• New resources are created immediately via the Konnect API.
• Existing resources are reconciled every 60 seconds 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.

The reconciliation loop runs once per minute. Wait 60 seconds, then refresh the UI.

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

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

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