You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@apisix.apache.org by "sober-wang (via GitHub)" <gi...@apache.org> on 2023/03/10 01:34:40 UTC
[GitHub] [apisix-ingress-controller] sober-wang commented on issue #610: proposal: New architecture of Apache APISIX Ingress controller
sober-wang commented on issue #610:
URL: https://github.com/apache/apisix-ingress-controller/issues/610#issuecomment-1463077886
> 
>
> I have a new idea.
>
> Since APISIX v3 has added the capability of gRPC-client, some optimizations have been made to the CP/DP deployment model in APISIX v3. So we can apply this model in APISIX Ingress, implement a gRPC server similar to ETCD in APISIX-Ingress-Controller, let it serve as the control plane, and APISIX, which is actually a data plane, connects to it through gRPC.
>
> In this way, the data plane APISIX is exactly the same as normal APISIX, not in Standalone mode, so you can use all the capabilities of APISIX without any modification to APISIX.
>
> WDYT?
look like , the apisix pull a configuretion from apisix-ingress-controller.
Apisix team member's will do it , Are you sure?
maybe , I'm misunderstand the means. So can you clarify the direction of data flow?
--
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-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org