From 0ce5ad9d5ada8db16038d99f023e924252bab1a9 Mon Sep 17 00:00:00 2001 From: salaboy Date: Tue, 21 May 2024 13:21:49 +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 afcf282e5..5deb79336 100644 --- a/daprdocs/content/en/operations/dapr-shared/dapr-shared.md +++ b/daprdocs/content/en/operations/dapr-shared/dapr-shared.md @@ -11,7 +11,7 @@ Dapr automatically injects a sidecar to enable the Dapr APIs for your applicatio 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. +- **`DaemonSet`:** When specifying to run Dapr as a Kubernetes `DaemonSet` resource, the daprd container runs on each Kubernetes node. This can reduce 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. {{% alert title="Dapr Shared deployments" color="primary" %}}