# 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 gateway workloads in Kubernetes. It is open source and self-hosted, installable on Kubernetes (Helm).

Canonical page: https://ourlocalhost.com/app/4883/kong-operator

## Description

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: Helm.

## Health score

65/100 (Good), based on 3 of 4 factors.
- Maintained: 100 (last commit 15 days ago)
- Popular: 41 (109 GitHub stars)
- Easy to install: 25 (1 install platform, install notes)

## Links

- Documentation: https://developer.konghq.com/operator/install/
- GitHub: https://github.com/Kong/kong-operator
- Kubernetes (Helm): https://artifacthub.io/packages/helm/kong/kong-operator

## 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.

---
Source: Our Local Host (https://ourlocalhost.com/app/4883/kong-operator), the self-hosted and open-source app directory.
