This is an automated email from the ASF dual-hosted git repository.
sylviasu pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/apisix-website.git
The following commit(s) were added to refs/heads/master by this push:
new 3279c4c948d docs: optimize “dapr with apisix” document (#1353)
3279c4c948d is described below
commit 3279c4c948d4a2c8500b4a5c05dee9fff43957cb
Author: oil欧呦 <[email protected]>
AuthorDate: Sat Oct 8 10:14:04 2022 +0800
docs: optimize “dapr with apisix” document (#1353)
* docs: improve dapr with apisix
* fix: update image
* fix: lint code
---
blog/en/blog/2021/11/17/dapr-with-apisix.md | 11 +++++++++--
blog/zh/blog/2021/11/17/dapr-with-apisix.md | 11 +++++++++--
2 files changed, 18 insertions(+), 4 deletions(-)
diff --git a/blog/en/blog/2021/11/17/dapr-with-apisix.md
b/blog/en/blog/2021/11/17/dapr-with-apisix.md
index 23b3c5acc09..ee351340804 100644
--- a/blog/en/blog/2021/11/17/dapr-with-apisix.md
+++ b/blog/en/blog/2021/11/17/dapr-with-apisix.md
@@ -36,7 +36,7 @@ In the K8s ecosystem, Ingress is a resource that represents
the entry point for
APISIX Ingress is another implementation of the Ingress Controller. The main
difference from Kubernetes Ingress Nginx is that APISIX Ingress uses Apache
APISIX as the actual data plane for hosting business traffic. As shown in the
figure below, when a user requests a specific service/API/web page, the entire
business traffic/user request is transferred to the K8s cluster through an
external proxy and then processed by APISIX Ingress.
-
+
As you can see from the above diagram, APISIX Ingress is divided into two
parts. One part is the APISIX Ingress Controller, which serves as the control
plane for configuration management and distribution. The other part is the
APISIX Proxy Pod, which is responsible for carrying business traffic and is
implemented through CRD (Custom Resource Definitions). Apache APISIX Ingress
supports not only custom resources but also native K8s Ingress resources.
@@ -132,9 +132,16 @@ Next, run the following command (referencing the above
file).
helm install apisix apisix/apisix -f dapr-annotations.yaml -n ingress-apisix
```
+Expose the launched APISIX Dashboard Pod to the outside world for subsequent
use:
+
+```shell
+# You can get the dashboard-pod-name via kubectl get pods -n ingress-apisix
+kubectl port-forward ${dashboard-pod-name} 9000:9000
+```
+
### Step 4: Create the Dapr Sidecar resource for Apache APISIX
-First, configure Apache APISIX upstream-apisix-dapr.
+First, access the APISIX Dashboard via `http://localhost:9000` to configure
Apache APISIX upstream-apisix-dapr.
diff --git a/blog/zh/blog/2021/11/17/dapr-with-apisix.md
b/blog/zh/blog/2021/11/17/dapr-with-apisix.md
index 499e8161752..a8f7f62b533 100644
--- a/blog/zh/blog/2021/11/17/dapr-with-apisix.md
+++ b/blog/zh/blog/2021/11/17/dapr-with-apisix.md
@@ -36,7 +36,7 @@ image:
https://static.apiseven.com/2022/blog/0818/ecosystem/dapr.png
而 APISIX Ingress 则是另一种 Ingress Controller 的实现。跟 Kubernetes Ingress Nginx
的区别主要在于 APISIX Ingress 是以 Apache APISIX
作为实际承载业务流量的数据面。如下图所示，当用户请求到具体的某一个服务/API/网页时，通过外部代理将整个业务流量/用户请求传输到 K8s 集群，然后经过
APISIX Ingress 进行后续处理。
-
+
从上图可以看到，APISIX Ingress 分成了两部分。一部分是 APISIX Ingress
Controller，作为控制面它将完成配置管理与分发。另一部分 APISIX Proxy Pod 负责承载业务流量，它是通过 CRD(Custom
Resource Definitions) 的方式实现的。Apache APISIX Ingress 除了支持自定义资源外，还支持原生的 K8s
Ingress 资源。
@@ -132,9 +132,16 @@ dashboard:
helm install apisix apisix/apisix -f dapr-annotations.yaml -n ingress-apisix
```
+将启动的 APISIX Dashboard Pod 向外暴露，便于后续使用：
+
+```shell
+# 可以通过 kubectl get pods -n ingress-apisix 获取 dashboard-pod-name
+kubectl port-forward ${dashboard-pod-name} 9000:9000
+```
+
### 步骤四：创建 Apache APISIX 的 Dapr Sidecar 资源
-首先，配置 Apache APISIX upstream-apisix-dapr。
+首先，通过 `http://localhost:9000` 访问 APISIX Dashboard 配置 Apache APISIX
upstream-apisix-dapr。
