ch-gr commented on issue #11338: URL: https://github.com/apache/apisix/issues/11338#issuecomment-3192142893
> 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 and https://docs.api7.ai/apisix/reference/apisix-ingress-controller/examples to understand the differences and upgrade steps. @juzhiyuan for Kubernetes, "[standalone mode without etcd](https://github.com/apache/apisix-ingress-controller/blob/2.0.0-rc3/docs/en/latest/install.md#install-apisix-and-apisix-ingress-controller-standalone-api-driven-mode)" seems to work: ```bash helm install apisix \ --namespace ingress-apisix \ --create-namespace \ --set apisix.deployment.role=traditional \ --set apisix.deployment.role_traditional.config_provider=yaml \ --set etcd.enabled=false \ --set ingress-controller.enabled=true \ --set ingress-controller.config.provider.type=apisix-standalone \ --set ingress-controller.apisix.adminService.namespace=ingress-apisix \ --set ingress-controller.gatewayProxy.createDefault=true \ apisix/apisix ``` But the documentation has an experimental tag in the [docs](https://github.com/apache/apisix/blob/3.13.0/docs/en/latest/deployment-modes.md#api-driven-experimental): ```text This mode is experimental, please do not rely on it in your production environment. We use it to validate certain specific workloads and if it is appropriate we will turn it into an officially supported feature, otherwise it will be removed. ``` And the current apisix helm chart (v2.11.5) uses a release candidate for the apisix-ingress-controller helm chart (v2.0.0-rc3). Is there a timeline for a GA release, with "standalone mode without etcd" as an officially supported feature, suitable for production environments? -- 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]
