juzhiyuan commented on issue #12461: URL: https://github.com/apache/apisix/issues/12461#issuecomment-3113337061
Hi @githubcdr, 1. For Apache APISIX Dashboard, there are no more separate Docker images. Since APISIX Gateway 3.13, every APISIX Docker image includes a built-in dashboard UI. It is a pure web UI composed of HTML, CSS, and JavaScript. Refer to https://github.com/apache/apisix-dashboard/issues/2981 and https://github.com/apache/apisix-dashboard/releases/tag/notice 2. For the Apache APISIX Gateway, the CVEs arise from the base image (e.g., Debian). We have made efforts to address these CVEs as much as possible. Last week, we switched the Debian image to Ubuntu, which has fewer CVEs. See https://hub.docker.com/layers/apache/apisix/3.13.0-ubuntu/images/sha256-08c2b033fe5ebca846fa6f806abd97f377683ee7060bda0dde003bc5bd8d6c85 3. ETCD is not maintained by the Apache APISIX team; it is maintained by Bitnami and it should be managed internally, so don't expose to the public network. 4. I noticed you are using K8s, and I suggest using APISIX Ingress Controller 2.0.0, which supports Kubernetes native deployment without ETCD. Refer to https://github.com/apache/apisix-ingress-controller/blob/master/docs/en/latest/upgrade-guide.md As for the helm chart still includes the Dashboard, @Baoyuantop we should remove it. -- 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-unsubscr...@apisix.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
