APISIX Ingress Controller

APISIX Ingress Controller is a Kubernetes controller that runs the Apache APISIX API Gateway as an ingress, dynamically configuring it using Kubernetes…

  • Development
  • Infrastructure
  • Tools & Utilities
APISIX Ingress Controller is a Kubernetes controller that runs the Apache APISIX API Gateway as an ingress, dynamically configuring it using Kubernetes Gateway API and Ingress resources. It is designed for platform teams who need a programmable, high-performance API gateway managed through standard Kubernetes APIs.

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.

75/100 Good

Maintained
100last commit 12 days ago
Popular
611,153 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
No data
Security check
81no serious findings, 2 minor, CI, tests, OpenSSF Scorecard 7.1/10

Based on 4 of 5 factors.

Availability: platform listings confirmed today

GitHub stars
1,153
Open issues
30
Last commit
2026-11-09
Latest release
2.2.0
License
Apache-2.0
Activity
declining

Checked 2 days ago - source: GitHub (apache/apisix-ingress-controller)

Resources & Compatibility

Requirements not published yet.

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

First-install notes

  • Start etcd before APISIX Start the etcd container before APISIX because etcd is a small database that stores APISIX routes and settings. If etcd isn’t running or APISIX can’t reach it, the gateway can’t load or update traffic rules. source
  • Point APISIX config at etcd and open ports Copy the example config.yaml and change the etcd URL to your etcd address, then expose 9080 for HTTP, 9443 for HTTPS, and 9180 for the Admin API (the control endpoint for adding routes). If the URL is wrong APISIX can’t reach its settings, and if those ports are closed you can’t use the gateway. source
  • Call Admin API, add service and route Before testing, use the Admin API with the X-API-KEY to create a service (the backend APISIX sends traffic to) and a route for your URL. Without the key APISIX rejects changes, and without the service/route it has nowhere to send requests. source

Fetched 53 days ago - each note links to its source

Alternatives (7)

  • BunkerWeb - BunkerWeb is a self-hosted, open-source web application firewall and NGINX-based web server that protects services with secure-by-default s…
  • Caddy - Caddy is an extensible web server and reverse proxy that serves Transport Layer Security (TLS) by default, making it simple to secure and r…
  • Corvus - Self-hosted reverse proxy and web application firewall with a web console; it provides domain forwarding, free SSL, live traffic monitoring…
  • HFS 2 (HTTP File Server) - You can use HFS (HTTP File Server) to send and receive files.
  • Microsoft IIS - Internet Information Services (IIS) for Windows® Server is a flexible, secure and easy-to-manage Web server for hosting anything on the Web.
  • lighttpd - Lighttpd is a secure, lightweight web server that uses memory and CPU more efficiently than comparable servers, with FastCGI, CGI, authenti…
  • nginx - Nginx is an HTTP web server, reverse proxy, content cache, load balancer, TCP/UDP proxy, and mail proxy server.

Checked 40 days ago - source: AlternativeTo

Common questions

Do I need to start etcd before APISIX?

Yes. Start the etcd container first and point the APISIX configuration at the etcd URL. If etcd isn't running or APISIX can't reach it, the gateway can't load or update traffic rules.

Which ports should be exposed for APISIX?

Expose 9080 for HTTP, 9443 for HTTPS, and 9180 for the Admin API. If those ports are closed, you can't use the gateway.

How do I create a service and route in APISIX?

Use the Admin API with the X-API-KEY to create the backend service and the route. Without the key APISIX rejects changes, and without a service and route it has nowhere to send requests.

How can I deploy APISIX Ingress Controller on Kubernetes?

The docs cover running APISIX on Kubernetes, installing APISIX with Helm, and using APISIX as a Kubernetes ingress / Gateway API implementation. Verify the selected documentation version before copying configuration or commands.

Answers sourced from apisix.apache.org, github.com, github.com

Community

Collected 48 days ago - public community threads