juzhiyuan commented on issue #11338: URL: https://github.com/apache/apisix/issues/11338#issuecomment-3162166205
Based on all the feedback and "solutions" collected in the past, here is a summary: 1. The currently **primary** supported deployment methods for APISIX are Docker (VM) and Helm (Kubernetes). 2. APISIX has three deployment modes: Traditional (with ETCD), Decoupled (with ETCD) and Standalone (**without** ETCD). Refer to https://docs.api7.ai/apisix/production/deployment-modes 3. For deployment modes that require ETCD, we strongly **recommend deploying ETCD on a VM**. When deploying to Kubernetes, scaling ETCD pods may result in such issues mentioned above (this issue is unrelated to APISIX itself). 4. If you are deploying APISIX on Kubernetes, we recommend controlling the 'apache/apisix' gateway via the **APISIX Ingress Controller 2.0+** The new design does not use ETCD, so you will not encounter these issues again. Please read https://github.com/apache/apisix-ingress-controller/blob/master/docs/en/latest/upgrade-guide.md to understand the differences and upgrade steps. -- 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]
