discuss: New feature in Apache APISIX Ingress controller v1.6

[tao12345666333]

Hi, folks

The Apache APISIX Ingress controller v1.5 version has been entered release window, and it is time to discuss the plans in the v1.6 version together.

I think the following features need to be included:

• Gateway API https://github.com/apache/apisix-ingress-controller/issues/644

  • #1217
  • #1278
  • HTTPRoute more complete support, such as filter

• #927

• #547

  • #1051

• Add suport for APISIX's plugin_metadata

[MBoui]

• Knative support ? :)

[tao12345666333]

• Knative support ? :)

thanks! SGTM

This will help us expand the ecosystem

[machinly]

Support multi cluster management should be helpful. ApisixClusterConfig was designed for this, but not completed.

[tao12345666333]

Support multi cluster management should be helpful. ApisixClusterConfig was designed for this, but not completed.

@machinly Are you referring to managing multiple APISIX clusters through one APISIX Ingress controller?

[tao12345666333]

In fact, we will achieve the goal of managing multiple APISIX instances through one Ingress controller. This is necessary for a complete implementation of the Gateway API.

We can dynamically state the APISIX instance simply by creating a Gateway resource.

[machinly]

Support multi cluster management should be helpful. ApisixClusterConfig was designed for this, but not completed.

@machinly Are you referring to managing multiple APISIX clusters through one APISIX Ingress controller?

The field parentRefs in HTTPRoute is exactly what I need. Gateway API is awesome.