Ingress Controller 2.1.0
This release adds richer route, Consumer, health-check, and admission-validation capabilities to both controllers.
Applies to:API7 Ingress Controller (drives API7 Gateway)APISIX Ingress Controller (drives Apache APISIX)
| Product | Released |
|---|---|
| APISIX Ingress Controller | 2026-06-01 |
| API7 Ingress Controller | 2026-05-29 |
This release adds richer route, Consumer, health-check, and admission-validation capabilities to both controllers. APISIX Ingress Controller also introduces listener-port matching; API7 Ingress Controller does not include that capability until 2.2.0.
Breaking Changes
APISIX Ingress Controller introduces one change that can affect existing Gateway API routes.
Align APISIX Listener Ports
APISIX Ingress Controller adds a server_port condition to some Gateway API routes and uses auto as the controller default. APISIX evaluates that condition against the physical port on which it accepted the connection. Requests return 404 when that port differs from the selected Gateway listener port.
API7 Ingress Controller 2.1.0 does not include port-based listener matching.
Upgrade: Set listener_port_match_mode to off or make the Gateway listener ports match the APISIX listener ports before rollout.
New Features
Both controllers expand their routing and resource-validation capabilities, with one APISIX-only addition.
Configure Richer Routes and Consumers
Both controllers add request-body matching to ApisixRoute, plugin configuration to ApisixConsumer, and Consumer labels derived from Kubernetes metadata. BackendTrafficPolicy can also configure active upstream health checks.
Validate Custom Resources Before Reconciliation
Both controllers add admission validation for APISIX custom resources. Invalid resources can be rejected before they reach translation and synchronization.
Match APISIX Routes by Listener Port
APISIX Ingress Controller adds port-based matching for Gateway API routes. API7 Ingress Controller adds this capability in 2.2.0.
Bug Fixes
The following fixes improve route translation, status reporting, synchronization, and health checks.
Route Translation and Status
- Regular-expression HTTPRoute paths no longer generate invalid URI matching.
- Gateway API route status conditions now update
observedGenerationcorrectly. - Status-only API resources no longer block controller readiness.
- HTTPRoute translation preserves a backend scheme that was already selected.
Synchronization and Health Checks
- Both controllers use HTTPS certificate verification for standalone active health checks when configured.
- APISIX Ingress Controller removes redundant route host configuration that caused persistent differences and unnecessary synchronization.