apache/apisix-ingress-controller 2.0.0-rc1

Release 2.0.0-rc1

on GitHub

Highlights

Add Gateway API Extensions apisix.apache.org/v1alpha1

Enable additional features not included in the standard Kubernetes Gateway API, developed and maintained by Gateway API implementers to extend functionality securely and reliably.

• GatewayProxy: Defines connection settings between the APISIX Ingress Controller and APISIX, including auth, endpoints, and global plugins. Referenced via parametersRef in Gateway, GatewayClass, or IngressClass

• BackendTrafficPolicy: Defines traffic management settings for backend services, including load balancing, timeouts, retries, and host header handling in the APISIX Ingress Controller.

• Consumer: Defines API consumers and their credentials, enabling authentication and plugin configuration for controlling access to API endpoints.

• PluginConfig: Defines reusable plugin configurations that can be referenced by other resources like HTTPRoute, enabling separation of routing logic and plugin settings for better reusability and manageability.

• HTTPRoutePolicy: Configures advanced traffic management and routing policies for HTTPRoute or Ingress resources, enhancing functionality without modifying the original resources.

Support APISIX Standalone API-Driven Mode (Experimental)

This new implementation addresses the issue of ETCD instability in Kubernetes, removing the need for ETCD support. Routing rules are now stored entirely in memory and can be updated through the API. This change allows you to run Ingress Controllers more reliably in a stateless mode.

You can enable this mode in APISIX Ingress Controller configuration file by specifying:

provider:
  type: "apisix-standalone"

For major changes introduced in this release, refer to the upgrade guide.

If you encounter any problems while using the implementation, please submit an issue along with the reproduction steps. The APISIX Team will review and resolve it.

Contributors

• AlinsRan
• Ashing Zheng

Changes