Stream Route is not getting configured via CRD but works well with Admin API

[Secret629]

Is stream routes created via CRDs works well or am I missing something. Below is the route properly synced but does not work where data-plane says no route found.

`
apiVersion: apisix.apache.org/v2
kind: ApisixRoute
metadata:
name: mqtt-stream-route
namespace: test

spec:
stream:

• backend:
  serviceName: activemq-service
  servicePort: 8883
  match:
  ingressPort: 8883
  name: mqtt-stream-proxy
  protocol: TCP
  status:
  conditions:
• message: Sync Successfully
  observedGeneration: 1
  reason: ResourcesSynced
  status: "True"
  type: ResourcesAvailable
  `

But creating route via Admin api works just fine
`{

	     "server_port": 8883,
	     "upstream": {
	       "type": "roundrobin",
	       "nodes": {
	         "activemq-service.test.svc.cluster.local:8883": 1
	       }
	     }
	   }`

[dosubot[bot]]

Stream routes (TCP/UDP) are not supported via CRDs in the APISIX Ingress Controller as of now—even if your CRD syncs and shows "ResourcesAvailable," the route will not be active in the data-plane. This is a known limitation, confirmed in the official documentation and CRD reference, which state that stream routes must be configured using the Admin API or standalone file mode, not CRDs.

The reason is architectural: the Ingress Controller manages HTTP routes, but stream routes use a separate subsystem that doesn't receive updates from CRDs (details). Recent updates have improved stream route support for Admin API and standalone mode (PR #12604), but CRD support is not included.

For now, keep using the Admin API for stream routes. If you need to automate or manage these routes declaratively, consider using standalone file mode or monitor the project for future CRD support.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}