Compatibility issue: unable to create stream route with APISIX v3.6

[brentmjohnson]

Current Behavior

Ingress controller fails to create stream route from apisix.apache.org/v2 ApisixRoute (working with apisix 3.5). Similar issue to #2003

Expected Behavior

Stream route is created successfully.

Error Logs

apisix ingress controller logs:

2023-10-24T22:04:39+08:00 error apisix/stream_route.go:143 failed to create stream_route: unexpected status code 400; error message: {"error_msg":"invalid configuration: additional properties forbidden, found labels"}
2023-10-24T22:04:39+08:00 error apisix/apisix_route.go:379 failed to sync ApisixRoute to apisix {"error": "1 error occurred:\n\t* unexpected status code 400; error message: {\"error_msg\":\"invalid configuration: additional properties forbidden, found labels\"}\n\n\n"}
2023-10-24T22:04:39+08:00 warn apisix/apisix_route.go:481 sync ApisixRoute failed, will retry {"object": {"Type":1,"Object":{"Key":"redpanda/redpanda-route","OldObject":null,"GroupVersion":"apisix.apache.org/v2"},"OldObject":null,"Tombstone":null}, "error": "1 error occurred:\n\t* unexpected status code 400; error message: {\"error_msg\":\"invalid configuration: additional properties forbidden, found labels\"}\n\n\n"}

apisix logs:

10.242.226.33 - - [24/Oct/2023:14:04:39 +0000] apisix-admin.ingress-apisix.svc.cluster.local:9180 "PUT /apisix/admin/stream_routes/d68fdff4 HTTP/1.1" 400 96 0.000 "-" "Go-http-client/1.1" - - - "http://apisix-admin.ingress-apisix.svc.cluster.local:9180"

Steps to Reproduce

Create a valid apisix.apache.org/v2 ApisixRoute resource like the following:

apiVersion: apisix.apache.org/v2
kind: ApisixRoute
metadata:
  name: redpanda-route
  namespace: redpanda
spec:
  stream:
    - name: rule1
      protocol: TCP
      match:
        ingressPort: 9092
      backend:
        serviceName: redpanda-external-headless
        servicePort: 9093

Environment

• APISIX version: 3.6.0
• APISIX Ingress controller version (run apisix-ingress-controller version --long): 1.7.0
• Kubernetes cluster version (run kubectl version): v1.28.3

[jiaozhentian]

Anyone fix this? We have same issue in env of APISIX 3.6.0 and k8s 1.27.6, installed by helm.

And this bug is not occurred in version of 3.5.0, hope fix it ASAP

[Revolyssup]

@jiaozhentian This issue is tracked here and I am working on it.

[github-actions[bot]]

This issue has been marked as stale due to 90 days of inactivity. It will be closed in 30 days if no further activity occurs. If this issue is still relevant, please simply write any comment. Even if closed, you can still revive the issue at any time or discuss it on the [email protected] list. Thank you for your contributions.

[github-actions[bot]]

This issue has been closed due to lack of activity. If you think that is incorrect, or the issue requires additional review, you can revive the issue at any time.