new diagrams

dapr · Jun 22, 2024 · 1fa3e22 · 1fa3e22
1 parent 2c812ea
commit 1fa3e22
Show file tree

Hide file tree

Showing 4 changed files with 1 addition and 1 deletion.
diff --git a/daprdocs/content/en/operations/hosting/kubernetes/kubernetes-dapr-shared.md b/daprdocs/content/en/operations/hosting/kubernetes/kubernetes-dapr-shared.md
@@ -32,7 +32,7 @@ While sidecars are Dapr's default deployment strategy, some use cases require ot
 Dapr Shared was created for these scenario, extending the Dapr sidecar model with two new deployment approaches: `DaemonSet` and `Deployment`.
 
 {{% alert title="Important" color="primary" %}}
-No matter which strategy you choose, it is important to understand that in most use cases, you will have one instance of Dapr Shared (Helm release) per service (app-id). This means that if you have an application composed of three microservices, each service is recommended to have its own Dapr Shared instance. Check the step-by-step tutorial using Kubernetes KinD to see an application using Dapr Shared.
+No matter which strategy you choose, it is important to understand that in most use cases, you have one instance of Dapr Shared (Helm release) per service (app-id). This means that if you have an application composed of three microservices, each service is recommended to have its own Dapr Shared instance. Try the `hello kubernetes` with Dapr Shared tutorial linked at the bottom of this page. 
 {{% /alert %}}
 
 

diff --git a/daprdocs/static/images/dapr-shared/daemonset.png b/daprdocs/static/images/dapr-shared/daemonset.png
diff --git a/daprdocs/static/images/dapr-shared/deployment.png b/daprdocs/static/images/dapr-shared/deployment.png
diff --git a/daprdocs/static/images/dapr-shared/sidecar.png b/daprdocs/static/images/dapr-shared/sidecar.png