Release Apache APISIX Ingress Controller 2.0

Published: 1 month ago (December 22, 2025 at 01:50 AM EST)

3 min read

Source: Dev.to

Overview

Built on the high‑performance API gateway Apache APISIX, the Ingress Controller has undergone multiple iterations and validations, now capable of handling large‑scale traffic management demands. This release brings substantial enhancements across three foundational pillars:

Comprehensive compatibility – full support for the latest Gateway API resources.
Adaptable architecture – flexible deployment options, including standalone and multi‑data‑plane modes.
Enterprise‑grade stability – reliable operation for production workloads.

Gateway API Support

APISIX Ingress Controller 2.0 expands Gateway API coverage with the addition of:

TCPRoute
UDPRoute
GRPCRoute
TLSRoute

These extensions provide native, protocol‑aware routing for HTTP, TCP/UDP, gRPC, and TLS passthrough/termination, enabling a unified configuration model for diverse ingress requirements.

API Extensions (apisix.apache.org/v1alpha1)

To address scenarios not covered by the standard Gateway API, APISIX introduces a set of vendor‑supported extensions that retain the core semantics of Gateway resources.

GatewayProxy

Defines the connection between the Ingress Controller and APISIX, including authentication, endpoints, and global plugins. Referenced via parametersRef in Gateway, GatewayClass, or IngressClass resources.

BackendTrafficPolicy

Fine‑grained traffic management for backend services (load balancing, timeouts, retries, host header handling).

Consumer

Specifies API consumers and their credentials, enabling authentication and plugin configuration for access control.

PluginConfig

Reusable plugin configurations that can be referenced by resources such as HTTPRoute, separating routing logic from plugin settings.

HTTPRoutePolicy

Advanced traffic management and routing policies for HTTPRoute or Ingress resources, enhancing functionality without modifying the original resources.

These extensions offer a standardized path to leverage advanced APISIX features directly within the Gateway API ecosystem.

Standalone (etcd‑Free) Mode

APISIX Ingress Controller 2.0 provides a lightweight deployment option that stores routing configurations entirely in memory. Updates are performed through a dedicated Standalone Admin API, which replaces the full configuration in a single operation and takes effect immediately via hot reloading—no restart required. This mode is primarily intended for integration with the API Declarative CLI (ADC).

Multi‑Data‑Plane Deployment

The release introduces flexible deployment options supporting multiple data‑plane modes, allowing a single Ingress Controller to manage several independent APISIX instances. This is ideal for scenarios requiring strict isolation, such as:

Multi‑tenancy
Staging vs. production environments
Region‑based routing

Centralized control is maintained while each data plane operates independently.

Traditional Deployment (etcd‑Based)

In the classic deployment model, APISIX uses etcd as its configuration center, enabling dynamic management of routes, upstreams, and other resources via RESTful APIs. It supports distributed cluster deployments with real‑time configuration synchronization.

Memory‑Based Standalone Mode (Kubernetes‑Optimized)

APISIX can also run without etcd, storing configurations in memory and managing them through the /apisix/admin/configs endpoint. This approach combines the convenience of the traditional Admin API with the simplicity of the standalone mode, making it well‑suited for Kubernetes and single‑node deployments.

Conclusion

Apache APISIX Ingress Controller 2.0 represents a significant evolution in Kubernetes ingress management. By uniting:

Comprehensive Gateway API support
Extensible configuration via official API extensions
A lightweight standalone deployment mode
Versatile multi‑data‑plane management

the release provides a cohesive foundation for dynamic cloud environments. It enables organizations to standardize ingress across diverse workloads, gain architectural flexibility, and achieve enterprise‑grade stability at scale.

For a complete list of features and changes, please refer to the [Release Changelog].