From 90a61296dc4a465c53c533d74c85b44db1578f3d Mon Sep 17 00:00:00 2001 From: Mark Fussell Date: Wed, 26 Jun 2024 13:06:44 -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 35af929b70e..4a61b776ad2 100644 --- a/daprdocs/content/en/operations/hosting/kubernetes/kubernetes-dapr-shared.md +++ b/daprdocs/content/en/operations/hosting/kubernetes/kubernetes-dapr-shared.md @@ -36,7 +36,7 @@ No matter which deployment approach you choose, it is important to understand th {{% /alert %}} -### `DeamonSet` strategy +### `DeamonSet`(Per-node) With Kubernetes `DaemonSet`, you can define workloads that need to be deployed once per node in the cluster. This enables workloads that are running on the same node to communicate with local Dapr APIs, no matter where the Kubernetes `Scheduler` schedules your workload.