# apache/apisix-ingress-controller

APISIX Ingress Controller for Kubernetes

Repository: https://github.com/apache/apisix-ingress-controller
Canonical: https://ross.abutalabs.com/products/apisix-ingress-controller
Homepage: https://apisix.apache.org/
Language: Go
License: Apache-2.0
License Family: permissive
Topics: ingress, controller, kubernetes, k8s, apigateway, microservices, api, loadbalancing, apisix, devops, crds, kubernetes-ingress
Last push: 2026-09-02T13:30:50+00:00

## Health v2 (maintenance only)
Score: 91/100 (v2, computed 2026-09-03T02:20:16.233290+00:00)
- activity 100, release rhythm 74, longevity 100
- inputs: {"age_days": 2485, "days_push": 0, "days_rel": 16, "gap_med": 133, "n_releases_24m": 6}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 1143, forks 389 (observed 2026-09-03T02:15:09.132799+00:00)

## What it is
A Kubernetes ingress controller that runs Apache APISIX as the gateway for handling inbound cluster traffic. It translates native Kubernetes Ingress, Gateway API, and APISIX CRD resources into APISIX configuration declaratively.

## Use cases
- expose kubernetes services to external traffic through an api gateway
- manage ingress routing declaratively with crds
- use gateway api resources with apisix as the data plane
- load balance traffic across pods in a kubernetes cluster
- apply rate limiting and authentication plugins at the cluster edge
- replace nginx ingress with a high-performance apisix gateway

## When to choose
- you already run or plan to run Apache APISIX and want Kubernetes-native configuration
- you need declarative CRD-based gateway configuration with rich plugin support
- you want Gateway API support with a high-performance NGINX-based proxy

## When to avoid
- you need a simple ingress without gateway features - the standard nginx ingress controller is lighter
- you are not on Kubernetes - use APISIX directly instead
- your cluster is older than Kubernetes 1.31

## Facets
- artifact type: service
- maturity: active
- function: api-gateway, routing, middleware, load-testing, deployment
- domain: microservices, apis, cloud-computing
- platform: go, cloud, self-hosted
- tags: ingress-controller, apisix, gateway-api, crds, k8s-operator, reverse-proxy, kubernetes, devops, docker

## Member repositories
- apache/apisix-ingress-controller (main) score 91

## Provenance
- Observed fields: from GitHub, fetched 2026-09-03T02:15:09.132799+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T06:34:54.967286+00:00, confidence not recorded.
  - readme: https://github.com/apache/apisix-ingress-controller (fetched 2026-09-03T02:15:09.132799+00:00, sha 2d73cbc482d5)
  - homepage: https://apisix.apache.org/ (fetched 2026-08-29T12:40:06.590582+00:00, sha fa1e21176f90)
  - site_page: https://apisix.apache.org/docs/apisix/getting-started/README (fetched 2026-08-29T12:40:06.593501+00:00, sha 7645c4d295a1)
  - site_page: https://apisix.apache.org/docs/ingress-controller/overview (fetched 2026-08-29T12:40:06.595725+00:00, sha 8520229ac418)
  - site_page: https://apisix.apache.org/docs/helm-chart/apisix (fetched 2026-08-29T12:40:06.597602+00:00, sha 7119cbf7ec3f)
  - site_page: https://apisix.apache.org/docs/docker/build (fetched 2026-08-29T12:40:06.599202+00:00, sha f6227f0ecc41)
  - site_page: https://apisix.apache.org/docs/java-plugin-runner/development (fetched 2026-08-29T12:40:06.600871+00:00, sha ca57f992f2ae)
  - site_page: https://apisix.apache.org/docs/go-plugin-runner/getting-started (fetched 2026-08-29T12:40:06.602745+00:00, sha f73de8159535)
  - site_page: https://apisix.apache.org/docs/python-plugin-runner/getting-started (fetched 2026-08-29T12:40:06.604544+00:00, sha 0c5247c917c0)
  - site_page: https://apisix.apache.org/docs/general/join (fetched 2026-08-29T12:40:06.606083+00:00, sha cdef87451d28)
- Data as of 2026-08-30T08:39:29.467469+00:00.