From 1f156e680675b42aee9546b283748859ecb85dc2 Mon Sep 17 00:00:00 2001 From: salaboy Date: Tue, 21 May 2024 13:21:26 +0100 Subject: [PATCH] Update daprdocs/content/en/operations/dapr-shared/dapr-shared.md Co-authored-by: Mark Fussell Signed-off-by: salaboy --- daprdocs/content/en/operations/dapr-shared/dapr-shared.md | 2 +- 1 file changed, 1 insertion(+), 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 57e23fa06d0..afcf282e58c 100644 --- a/daprdocs/content/en/operations/dapr-shared/dapr-shared.md +++ b/daprdocs/content/en/operations/dapr-shared/dapr-shared.md @@ -9,7 +9,7 @@ description: "Learn more about using Dapr Shared as an alternative deployment to Dapr automatically injects a sidecar to enable the Dapr APIs for your applications for the best availability and reliability. -Dapr Shared enables different deployment strategies to create Dapr applications using Kubernetes `Daemonset` or `Deployment`. +Dapr Shared enables two alternative deployment strategies to create Dapr applications using a Kubernetes `Daemonset`for a per-node deployment or a`Deployment` for a per-cluster deployment. - **`DaemonSet`:** When running daprd as a Kubernetes `DaemonSet` resource, the daprd container runs in each Kubernetes node, reducing network hops between the applications and Dapr. - **`Deployment`:** When running Dapr Shared as a Kubernetes `Deployment`, the Kubernetes scheduler decides in which node the Dapr Shared instance will run.