You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@apisix.apache.org by ju...@apache.org on 2021/12/07 05:55:09 UTC

[apisix-website] branch master updated: docs: update Dapr blog EN version images (#795)

This is an automated email from the ASF dual-hosted git repository.

juzhiyuan 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 b0ebae1  docs: update Dapr blog EN version images (#795)
b0ebae1 is described below

commit b0ebae1fbd137281fc026f85eb209269eb41e11c
Author: Sylvia <39...@users.noreply.github.com>
AuthorDate: Tue Dec 7 13:55:06 2021 +0800

    docs: update Dapr blog EN version images (#795)
---
 website/blog/2021/11/17/dapr-with-apisix.md | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/website/blog/2021/11/17/dapr-with-apisix.md b/website/blog/2021/11/17/dapr-with-apisix.md
index 1571119..8e05a7a 100644
--- a/website/blog/2021/11/17/dapr-with-apisix.md
+++ b/website/blog/2021/11/17/dapr-with-apisix.md
@@ -21,7 +21,7 @@ Essentially, the Apache APISIX controller will configure the same standard DAPR
 
 The following diagram shows the architectural flow of the actual project:
 
-![Overview](https://static.apiseven.com/202108/1637119221118-75dab9f1-4092-4684-ad23-34932d8a7eac.png)
+![Overview](https://static.apiseven.com/202108/1638855752235-121756ab-f5b7-489f-af42-0c3f962b3036.png)
 
 ## Overview
 
@@ -131,7 +131,7 @@ helm install apisix apisix/apisix -f dapr-annotations.yaml -n ingress-apisix
 
 First, configure Apache APISIX upstream-apisix-dapr.
 
-![Create the Dapr Sidecar](https://static.apiseven.com/202108/1637119221106-e57ae8b8-38ed-46ea-b219-401619fadbe3.png)
+![Create the Dapr Sidecar](https://static.apiseven.com/202108/1638855797186-a9b940e2-4d56-4a6d-a621-ea615ddba0dd.png)
 
 Fill in the hostname here: apisix-gateway-dapr and the port number 3500.
 
@@ -159,7 +159,7 @@ Fill in the hostname here: apisix-gateway-dapr and the port number 3500.
 
 Then configure the Apache APISIX service apisix-gateway-dapr, and select apisix-dapr for the upstream service.
 
-![Configuration service](https://static.apiseven.com/202108/1637119221115-ae7c847a-99a3-4ee6-b36f-4269fd067198.png)
+![Configuration service](https://static.apiseven.com/202108/1638855804018-094559fd-a1df-4184-becd-9bfbf0018339.png)
 
 ```json
 {
@@ -178,7 +178,7 @@ kubectl apply -f 02.deployment.yaml
 kubectl apply -f 03.svc.yaml
 ```
 
-![Project configuration](https://static.apiseven.com/202108/1637119221110-9b901451-6ca6-4d15-b591-69f7c5d57ce1.png)
+![Project configuration](https://static.apiseven.com/202108/1638855818560-9ae75e39-9ed2-4796-a9eb-ebf66b07c1e5.png)
 
 The image above shows a hypothetical microservice running with the Dapr app-id kennethreitz-httpbin.
 
@@ -186,7 +186,7 @@ The image above shows a hypothetical microservice running with the Dapr app-id k
 
 Here we add some settings related to path matching. For example, if the request gateway is /httpbin/, the backend receive path should be /, with httpbin acting as a service name identifier.
 
-![Interpretation](https://static.apiseven.com/202108/1637119221114-90c1ef58-6743-419c-be87-9cdc8503aa30.png)
+![Interpretation](https://static.apiseven.com/202108/1638855827906-2aafa04c-a00c-4d41-aeb2-663c1f999dcd.png)
 
 On hosted platforms that support namespaces, the Dapr application ID is in a valid FQDN format, which includes the target namespace. For example, the following string contains the application ID (svc-kennethreitz-httpbin) and the namespace the application is running in (kind-test).