bzp2010 commented on issue #2527:
URL: 
https://github.com/apache/apisix-ingress-controller/issues/2527#issuecomment-3232502105

   @ronething 
   
   What's holding us back from achieving it?
   
   ADC has already achieved synchronization for stream services and stream 
routes. This applies to both Admin API + etcd and the new standalone mode.
   
   > However, it must be noted that there is an issue with stream route 
configuration loading in APISIX standalone. This prevents the APISIX data plane 
from actually loading the configuration.
   > Nevertheless, both ADC and APISIX standalone API already support this 
functionality. This won't prevent you from issuing ADC configurations and 
synchronizing them. Testing might encounter obstacles.
   
   I believe stream route use cases on APISIX standalone should be supported. 
This is not limited to stream configurations in ApisixRoute (to my knowledge, 
we won't evolve this standard further but maintain it before eventual 
deprecation). TCPRoute/UDPRoute in the Gateway API similarly rely on this 
functionality for correct operation.
   
   We need to establish a plan: first, adapt the standalone implementation in 
APISIX to support stream routes, which I believe **MUST** be guaranteed for 
release in 3.14 at the latest. Subsequently, implement it in the Ingress 
Controller.
   
   I will create an issue in APISIX to track progress there, while in the 
Ingress Controller, I will include it in a later milestone.


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

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to