Gateway Operator

Kong Gateway Operator is a Kubernetes operator that installs, configures, and manages the Kong Ingress Controller and Kong Gateway data plane in your cluster,…

  • Development
  • Infrastructure
  • Tools & Utilities
Kong Gateway Operator is a Kubernetes operator that installs, configures, and manages the Kong Ingress Controller and Kong Gateway data plane in your cluster, letting you deploy, upgrade (rolling or blue/green), and autoscale Kong as your API and Ingress gateway.

Platform availability

Available on 1 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

65/100 Good

Maintained
100last commit 1 day ago
Popular
41111 GitHub stars
Easy to install
251 install platform, install notes
Light to run
No data

Based on 3 of 4 factors.

Availability: platform listings confirmed today

GitHub stars
111
Open issues
220
Last commit
2026-11-20
Latest release
v2.4.0
License
Apache-2.0
Activity
steady

Checked today - source: GitHub (Kong/gateway-operator)

Resources & Compatibility

Requirements not published yet.

First-install notes

  • Start the server with its config file From the example folder that contains envoy-gateway.yaml, run `envoy-gateway server --config-path envoy-gateway.yaml`. This starts Envoy Gateway in standalone mode (a self-contained way to run it) using the intended settings; without pointing to the right file, it can fail or run without the rules you expect. source

Fetched 41 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Can Kong Operator manage Kong Ingress Controller and Gateway data planes together?

Yes, it can manage Kong Ingress Controller, Kong Gateway Data Planes, or both together on Kubernetes.

Can I customise the Pod template for DataPlane deployments?

Yes, you can use PodTemplateSpec to customise deployments, including deploying sidecars and setting the image.

How can Data Plane upgrades be performed?

The operator supports Data Plane upgrades using rolling restarts or blue/green deployments.

What stability guarantee applies to the operator APIs?

The YAML/manifests API follows Kubernetes API versioning and is considered part of the user contract. The Go API tries to avoid breaking changes but has no non-breaking guarantee.

Answers sourced from github.com

Community

Collected 48 days ago - public community threads