juzhiyuan commented on issue #2514: URL: https://github.com/apache/apisix-ingress-controller/issues/2514#issuecomment-3578354337
> Full Configuration Push on Updates I'll leave it to @bzp2010 for better explanation. > No Persistence & Recovery Downtime In the Production environment, we should configure `/healthz` and `/liveness` correctly to handle traffic after the new Pods are in Ready state. > Lack of Dashboard Support: The APISIX Dashboard does not work without etcd, which removes a critical tool for observability and troubleshooting. Starting with _apache/apisix 3.13_, the APISIX Dashboard[1] is built as pure HTML/CSS/JS files and included in the _apache/apisix_ Docker image, and you can access it via _apisix:9180/ui_. It only fetches configurations through the _APISIX Admin API_[2]. The APISIX Dashboard is just a wrapper of the Admin API. I don't see how it relates to Observability because, according to the _Dashboard Scopes_[3], we don't plan to add such functionalities. We recommend that users connects with external observability components using the APISIX built-in observability plugins[4] for professional experience. [1] https://github.com/apache/apisix-dashboard [2] https://docs.api7.ai/apisix/reference/admin-api [3] https://github.com/apache/apisix-dashboard/issues/2981 [4] https://docs.api7.ai/hub#observability -- 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]
