Skip to content
Kong Docs are moving soon! Our docs are migrating to a new home. You'll be automatically redirected to the new site in the future. In the meantime, view this page on the new site!
|
1.3.x
github-edit-pageEdit this page
report-issueReport an issue
You are browsing documentation for an older version. See the latest documentation here.

FAQ

How can I use the Kong Gateway Operator?

You can install the Kong Gateway Operator by following the instructions in the installation guide.

The quickest way to get started is to attach your data planes to Konnect. For more information, see the getting started with Konnect.

How can I get help with the Kong Gateway Operator?

If you’re a Kong Gateway Enterprise customer, please raise a support ticket. If you’re an Open Source user, please create an issue in Kong/gateway-operator-docs/

Will you still support the Kong Helm chart?

Yes. The Kong Helm chart is the primary way that customers install Kong today, and we’re committed to maintaining it going forward. Helm will always support any functionality that needs to be configured during installation, but will not support any day-2 operations.

How is this different from Helm?

Helm follows a more procedural approach to deployment, where you define the sequence of actions to be performed during installation or upgrade. Operators, on the other hand, are built on a declarative model. They observe the desired state defined in custom resources and ensure that the actual state of the system matches it. This declarative approach allows Operators to continuously reconcile and maintain the desired state, making them more robust and resilient.