leslie-tsang commented on code in PR #8849:
URL: https://github.com/apache/apisix/pull/8849#discussion_r1109527242
##########
docs/zh/latest/FAQ.md:
##########
@@ -707,6 +707,21 @@ make GOOS=linux GOARCH=amd64
prefix: "/apisix"
```
+## APISIX 如何配置带认证的 ETCD
+
+假设您有一个启用身份验证的 ETCD 集群。要访问该集群，需要为 Apache APISIX
配置正确的用户名和密码。需要配置`conf/config.yaml` 文件，添加如下内容：
+
+```yaml
+deployment:
+ etcd:
+ host:
+ - "http://127.0.0.1:2379";
+ user: root # root username for etcd
+ password: 5tHkHhYkjr6cQY # root password for etcd
+```
+
+关于 ETCD 的其他配置，比如过期时间、重试次数等等，你可以查看`conf/config-default.yaml`文件中的`ETCD`部分。
Review Comment:
```suggestion
关于 ETCD 的其他配置，比如过期时间、重试次数等等，你可以参考 `conf/config-default.yaml` 文件中的 `ETCD` 部分。
```
##########
docs/zh/latest/FAQ.md:
##########
@@ -707,6 +707,21 @@ make GOOS=linux GOARCH=amd64
prefix: "/apisix"
```
+## APISIX 如何配置带认证的 ETCD
+
+假设您有一个启用身份验证的 ETCD 集群。要访问该集群，需要为 Apache APISIX
配置正确的用户名和密码。需要配置`conf/config.yaml` 文件，添加如下内容：
Review Comment:
```suggestion
假设您有一个启用身份验证的 ETCD 集群。要访问该集群，需要为 Apache APISIX 配置正确的用户名和密码。需要配置
`conf/config.yaml` 文件，添加如下内容：
```
##########
docs/en/latest/FAQ.md:
##########
@@ -704,6 +704,21 @@ Another solution is to switch to an experimental
gRPC-based configuration synchr
prefix: "/apisix"
```
+## How does APISIX configure ETCD with authentication
+
+Suppose you have an ETCD cluster that enables the auth. To access this
cluster, you need to configure the correct username and password for Apache
APISIX. Edit the `conf/config.yaml` file as follows:
+
+```yaml
+deployment:
+ etcd:
+ host:
+ - "http://127.0.0.1:2379";
+ user: root # root username for etcd
+ password: 5tHkHhYkjr6cQY # root password for etcd
Review Comment:
```suggestion
user: etcd_user # root username for etcd
password: etcd_password # root password for etcd
```
Would be better to don‘t have a specific password, Misunderstandings may
arise.
--
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]
