Kong Ingress Controller

Kong Ingress Controller (KIC) is a Kubernetes-native controller that uses the Kong API gateway to route, secure, and load-balance inbound traffic to your…

  • Development
  • Infrastructure
  • Tools & Utilities
Kong Ingress Controller (KIC) is a Kubernetes-native controller that uses the Kong API gateway to route, secure, and load-balance inbound traffic to your services. It implements the Kubernetes Ingress and Gateway API standards, letting teams configure plugins, health checking, and more through custom resource definitions (CRDs) with standard Kubernetes tooling.

Platform availability

Available on 0 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • 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.

74/100 Good

Maintained
100last commit 2 days ago
Popular
682,415 GitHub stars
Easy to install
250 install platforms, install notes, Docker image
Light to run
No data
Security check
78no serious findings, 4 minor, CI, tests, OpenSSF Scorecard 8.2/10

Based on 4 of 5 factors.

GitHub stars
2,415
Open issues
296
Last commit
2026-11-19
Latest release
v3.5.14
License
Apache-2.0
Activity
declining

Checked 2 days ago - source: GitHub (Kong/kubernetes-ingress-controller)

Resources & Compatibility

Requirements not published yet.

Checked 23 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Prepare the database before starting Kong On a fresh datastore, run `kong migrations bootstrap` before `kong start`, using `-c` to point to your config file if needed. This creates the required database schema, and skipping it can make Kong fail at startup with errors about a missing or outdated schema. source
  • Use the right Kong config file By default Kong reads `/etc/kong/kong.conf`, or you can pass a custom file with `-c /path/to/kong.conf`. This file contains important settings such as datastore connection details, so the wrong path can prevent Kong from finding its database or starting correctly. source

Fetched 53 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Do I need to install Gateway API CRDs before using Gateway API with Kong Ingress Controller?

Yes, install the standard or experimental Gateway API CRDs before configuring GatewayClass, Gateway, HTTPRoute, or ReferenceGrant. This makes the required Gateway API resources available to Kong Ingress Controller.

What must I run on a fresh Kong datastore before starting Kong?

Run kong migrations bootstrap before kong start to create the required database schema. Skipping this can make Kong fail at startup with missing or outdated schema errors.

Which Kong configuration file does Kong read by default?

Kong reads /etc/kong/kong.conf by default, and you can point it to another file with -c /path/to/kong.conf. A wrong path can prevent Kong from finding its database or starting.

Answers sourced from github.com, github.com

Community

Collected 48 days ago - public community threads