tao12345666333 opened a new issue #610: URL: https://github.com/apache/apisix-ingress-controller/issues/610
In the current architecture of the Apache APISIX Ingress controller, we use the Apache APISIX Ingress controller as a control plane component. The user creates a specified type of CR in Kubernetes, and the Apache APISIX Ingress controller converts it into a data structure that can be received by Apache APISIX, and creates, modifies or deletes it by calling the admin API. Such an architecture has the following advantages: - The separation of CP and DP can ensure that even if the CP component is abnormal, DP can still run properly; - Users can deploy DP in any location they like, including outside the Kubernetes cluster But such an architecture will also have its disadvantages Users need to maintain a complete Apache APISIX cluster, which cannot be done simply by modifying the replicas field of the Apache APISIX Ingress controller I hope to introduce an architecture similar to ingress-nginx, which is widely used in Kubernetes. In this way, users can complete the deployment directly through a Pod. At the same time, user can simply modify the replicas parameter to complete the scale. sync from mail list: https://lists.apache.org/thread.html/r929a6dfa9620d96874056750c6b07b8139b4952c8f168670553dfb86%40%3Cdev.apisix.apache.org%3E -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
