From d96d0a8495f8c32103ed3437f397e5dcb1826339 Mon Sep 17 00:00:00 2001 From: salaboy Date: Wed, 5 Jun 2024 13:45:25 +0100 Subject: [PATCH] Update daprdocs/content/en/operations/dapr-shared/dapr-shared.md Co-authored-by: Hannah Hunter <94493363+hhunter-ms@users.noreply.github.com> Signed-off-by: salaboy --- daprdocs/content/en/operations/dapr-shared/dapr-shared.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/daprdocs/content/en/operations/dapr-shared/dapr-shared.md b/daprdocs/content/en/operations/dapr-shared/dapr-shared.md index 93435ab06..154bce4dc 100644 --- a/daprdocs/content/en/operations/dapr-shared/dapr-shared.md +++ b/daprdocs/content/en/operations/dapr-shared/dapr-shared.md @@ -32,7 +32,9 @@ 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`. -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 by three microservices, each service is recommended to have it's own Dapr Shared instance. Check the step-by-step tutorial using Kubernetes KinD here, to see an application using Dapr Shared. +{{% 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. +{{% /alert %}} ### `DeamonSet` strategy