ronething opened a new issue, #2527: URL: https://github.com/apache/apisix-ingress-controller/issues/2527
### Current Behavior As the PR https://github.com/apache/apisix-ingress-controller/pull/2522 mentioned, currently, we do not support configuring stream rules in the `Apisixroute`, but we have not blocked it, which may cause confusion to users. ref: https://github.com/apache/apisix-ingress-controller/blob/6bc3731a5c7fee65fe7e1f141484272843ab2bfa/internal/controller/apisixroute_controller.go#L155-L159 ### Expected Behavior consider update apisixroute status to error status instead of accepted. ### Error Logs _No response_ ### Steps to Reproduce Configure the corresponding rules on spec.stream of `apisixroute` ### Environment - APISIX Ingress controller version (run `apisix-ingress-controller version --long`) - Kubernetes cluster version (run `kubectl version`) - OS version if running APISIX Ingress controller in a bare-metal environment (run `uname -a`) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@apisix.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
