Apache APISIX Ingress v1.5-rc1 released

Apache APISIX Ingress Controller v1.5-rc1 is officially released.This release took about 7 months and had 144 commits by 36 contributors.Among them, there are 22 new contributors, thank you for your contribution and support to this project!

NextLet's take a look at the important updates in APISIX Ingress v1.5.

All CRD API Versions are upgraded to v2

At the beginning of the APISIX Ingress project, there are only a few CRDs, and each resource is maintained by its own API Version.This leads to a situation where the API Version used by each custom resource is different in the process of subsequent introduction of new resources or function iteration, which increases user learning costs.

So starting from the v1.3 version, we propose a unified API Version of all resources

Proposal

.After two version iterations, the v2 API Version has been officially introduced, and v2beta3 is marked as deprecated, and v2beta3 will be completely removed until the v1.7 version.

Basically support Gateway API

Gateway API can be said to be the next generation of Ingress definition, with richer performance capabilities.We have completed support for most of these resources in APISIX Ingress (note that this feature is currently experimental and not enabled by default).

If you want to use the Gateway API in APISIX Ingress, you can pass it in the controller's configuration file

enable_gateway_api: true

configuration item to enable this feature.

After installing the CRD of the Gateway API, you can complete the 7th layer by creating

HTTPRoute

resourcesProxy configuration.It looks like this:

apiVersion: gateway.networking.k8s.io/v1alpha2
kind: HTTPRoute
metadata:
name: httpbin-route
spec:
hostnames: ["httpbin.local"]
rules:
- matches:
- path:
type: PathPrefix
value:/ip
backendRefs:
- name: httpbin
port: 80


After this configuration takes effect, the client will be able to pass

httpbin.local/ip

Access to port 80 of the backend httpbin.

In addition, we plan to implement the remaining Gateway API in v1.6

TCPRoute

and

UDPRoute

These two resources are supported, and a conformance test for the Gateway API is planned to be introduced to ensure that our implementation is consistent with the expectations of the Gateway API.

Allow Ingress resources to bind any plugins

In the Apache APISIX Ingress Controller project, it supports proxy configuration using Kubernetes native Ingress resources, but if you want to use APISIX in Ingress resourcesRich plug-in capabilities must be completed by adding Annotation, and the logic corresponding to Annotation needs to be implemented.

This approach limits the plugin capabilities of Ingress resources, and developing Annotaion separately for each plugin is relatively expensive.

In v1.5, we added a new Annotaion to the Ingress resource by adding a

k8s.apisix.apache.org/plugin-config-name

, which allows to refer to any

ApisixPluginConfig

resource, thus enabling the Ingress resource to be freeAbility to use any APISIX plugin.This will greatly increase the ease of use of APISIX Ingress Controller, and will also reduce the cost for users to migrate from other Ingress Controllers to APISIX Ingress Controller.

More Details

In addition to these features, many other features have been added to this release.For example:

• The mechanism for synchronizing data from the Kubernetes cluster to the APISIX cluster at regular intervals to ensure the consistency between the data in the APISIX cluster and the configuration in the Kubernetes cluster;

• Add more authentication methods for ApisixConsumer resources;

• and APISIXCompatible with v2.15;

• Update all dependencies to the latest version to reduce security risks;

For more specific release details, please refer to

Changelog

of 1.5-rc1