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 feat: GatewayAPI Support #644

  • * feat: support gateway/tcproute #1217
  • * feat: add Gateway UDPRoute #1278
  • * feat: add support for Gateway API HTTPRouteFilter #1418 HTTPRoute more complete support, such as filter

• Proposal: support external name service #927

  • feat: support external service #1306

• feat: Support SNI based TLS Route #547

  • feat: support sni based tls route #1051

• Proposal: Add support for APISIXPluginMetadata function #1372 Add suport for APISIX's plugin_metadata

  • feat: support plugin_metadata of apisix #1369

• Proposal: Apisix-Ingress-Controller support integrating with service discovery registry #1019 and feat: Support for 'discovery_type' in ApisixUpstream #948

• proposal: use a uniform CRD APIVersion #707

  • chore: remove v2beta2 API Version #1431

• feat: support k8s native ingress and backend service in the different namespace #1374

  • feat: support k8s native ingress and backend service in different… #1377

• feature request: ApisixRoute resources use vars in Route #1376

• Feature suggestion: support stream route with plugins #744

• feat request: native MQTT Protocol proxy  #966

[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.

[tao12345666333]

v1.6.0-rc1 has been released. #1536 I will close this one. Thanks all!!!