Kong Operator

Kong Operator is a Kubernetes operator that deploys, configures, and upgrades Kong Gateway data planes and Kong Ingress Controller for teams running API…

  • Development
  • Infrastructure
  • Tools & Utilities
Kong Operator is a Kubernetes operator that deploys, configures, and upgrades Kong Gateway data planes and Kong Ingress Controller for teams running API gateway workloads in Kubernetes.

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 15 days ago
Popular
41109 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
109
Open issues
262
Last commit
2026-11-06
Latest release
v2.4.0-rapid.3.1
License
Apache-2.0
Activity
rising

Checked 14 days ago - source: GitHub (Kong/kong-operator)

Resources & Compatibility

Requirements not published yet.

First-install notes

  • Install Install Kong Operator with Helm, optionally enabling cert-manager to manage admission and conversion webhook certificates. source

Fetched 41 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Do I need one Kong Operator per Kong instance?

No. The operator watches Kong custom resources and deploys a Kong instance for each one, so one operator can typically manage multiple Kong instances per cluster.

Can Kong Operator work with a self-hosted control plane?

Yes. Kong Operator architecture can use either a self-hosted control plane or Konnect for single-tenant and multi-tenant deployments.

What Kubernetes objects drive Kong Operator configuration?

Kong Operator is driven by Gateway API or Kong-specific custom resource definitions, allowing declarative deployment and configuration of Kong products.

Answers sourced from developer.konghq.com, developer.konghq.com, discuss.konghq.com

Community

Collected 48 days ago - public community threads