Skip to main content
Version: Next

Overview

APISIX Ingress Controller is a Kubernetes ingress controller using Apache APISIX as the high performance reverse proxy.

APISIX Ingress Controller can be configured using the native Kubernetes Ingress or Gateway API, as well as with APISIX’s own declarative and easy-to-use custom resources. The controller translates these resources into APISIX configuration.

See the Getting Started tutorials to set up and start using the APISIX Ingress Controller.

Features#

To summarize, APISIX ingress controller has the following features:

  • Declarative configuration with CRDs.
  • Supports native Kubernetes Ingress v1 and Gateway API.
  • Supports service discovery through Kubernetes Service.
  • Supports load balancing based on pods (Upstream nodes).
  • Rich Plugins with custom Plugin support.

Get involved#

You can contribute to the development of APISIX ingress controller. See Development guide for instructions on setting up the project locally.

See the Contribute to APISIX section for details on the contributing flow.

Compatibility with APISIX#

The table below shows the compatibility between APISIX ingress controller and the APISIX proxy.

note

APISIX Ingress Controller 2.0.0+ support the APISIX Standalone API-driven Mode, but require APISIX 3.13+.

APISIX ingress controllerSupported APISIX versionsRecommended APISIX version
master>=3.03.13
2.0.0>=3.03.13
1.6.0>= 2.15, >=3.02.15, 3.0
1.5.0>= 2.72.15
1.4.0>= 2.72.11
1.3.0>= 2.72.10
1.2.0>= 2.72.8
1.1.0>= 2.72.7
1.1.0>= 2.72.7
1.0.0>= 2.72.7
0.6>= 2.62.6
0.5>= 2.42.5
0.4>= 2.4