Apache APISIX Ingress Controller enables Kubernetes users to declaratively manage API gateway configurations with advanced traffic control, security, and load balancing features.
APISIX Ingress Controller for Kubernetes
This tool is used by Kubernetes administrators and DevOps engineers to manage ingress traffic in Kubernetes clusters using Apache APISIX as the API gateway. It simplifies API security, load balancing, and SSL/mTLS configuration through Kubernetes-native Custom Resource Definitions, enabling dynamic and scalable traffic management.
The controller requires Kubernetes 1.16+ due to reliance on stable CRD v1 API and Apache APISIX 2.7+ for compatibility. Users should avoid modifying resources labeled 'managed-by: apisix-ingress-controllers' via APISIX Dashboard to prevent conflicts. The control plane and data plane separation enhances security and deployment flexibility. Hot-reload support allows immediate application of configuration changes without downtime.
Ensure Kubernetes version 1.16+ is installed
Ensure Apache APISIX version 2.7+ is deployed
Follow installation guide in install.md file
Apply Kubernetes manifests for apisix-ingress-controller
Configure necessary CRDs for ingress and routing
Deploy apisix-ingress-controller in the Kubernetes clusterkubectl apply -f apisix-ingress-controller.yaml
Deploys the APISIX Ingress Controller into the Kubernetes cluster
kubectl apply -f ingress-resource.yaml
Applies a Kubernetes Ingress resource that the controller will manage
kubectl get apisixroutes
Lists APISIX route resources managed by the ingress controller
kubectl describe apisixroutes <route-name>
Shows detailed information about a specific APISIX route