You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@apisix.apache.org by GitBox <gi...@apache.org> on 2021/10/14 05:00:17 UTC

[GitHub] [apisix-ingress-controller] gxthrj commented on issue #712: request help: apisix-ingress-controller "error": "unexpected non-empty object"

gxthrj commented on issue #712:
URL: https://github.com/apache/apisix-ingress-controller/issues/712#issuecomment-942948209


   It is theoretically feasible to let APISIX serve the k8s cluster and other virtual machine clusters at the same time. But there are a few things to note:
   1. The ingress-controller needs to be able to access the APISIX admin API normally, and you need to ensure that the network is smooth. Of cause, APISIX also needs to be able to access k8s internal services
   2. The dashboard only manages the virtual machine cluster, not the k8s cluster. The configuration management in the k8s cluster is handled by the ingress controller.
   


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