[GitHub] [apisix-ingress-controller] tokers commented on issue #669: request help: Why using apisix admin api but not modify the data in etcd?

[GitBox <gi...@apache.org>]

tokers commented on issue #669:
URL: https://github.com/apache/apisix-ingress-controller/issues/669#issuecomment-914341986


   > I think use apisix admin api to do schema things has becoming a problem.It has led to some unnecessary coupling.
   > In apisix-dashboard,some schema feature must depend on apisix admin api too, this is really not good.
   > How about separating those functions from apisix, make data panel more pure, only communicate with etcd(include register schema information to etcd).Then we offer a common sdk or service to get or verify schema infomation for other service like ingress-controll or dashboard.
   
   We cannot fetch the first feedback from the config users, i.e. APISIX cluster, if we just write data to ETCD, we won't know any incompatible problems or bugs, instead, Admin APIs do this so we can record the kinds of errors to CRD status or error log, and, the bad config will not be persistent.


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