From daeb6a2e7056270d72301ba3fe0745583bd41237 Mon Sep 17 00:00:00 2001 From: Mark Fussell Date: Wed, 26 Jun 2024 13:19:27 -0700 Subject: [PATCH] Update daprdocs/content/en/operations/hosting/kubernetes/kubernetes-dapr-shared.md Signed-off-by: Mark Fussell --- .../en/operations/hosting/kubernetes/kubernetes-dapr-shared.md | 2 +- 1 file changed, 1 insertion(+), 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 index 31e7f8b5b15..4bef59fe6e1 100644 --- a/daprdocs/content/en/operations/hosting/kubernetes/kubernetes-dapr-shared.md +++ b/daprdocs/content/en/operations/hosting/kubernetes/kubernetes-dapr-shared.md @@ -12,7 +12,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 Dapr Shared as a Kubernetes `DaemonSet` resource, the daprd container runs on each Kubernetes node in the cluster. 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. +- **`Deployment`:** When running Dapr Shared as a Kubernetes `Deployment`, the Kubernetes scheduler decides on which single node in the cluster the daprd container instance runs. {{% alert title="Dapr Shared deployments" color="primary" %}} For each Dapr application you deploy, you need to deploy the Dapr Shared Helm chart using different `shared.appId`s.