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 <Salaboy@gmail.com>
This commit is contained in:
salaboy 2024-05-07 17:48:43 +01:00
parent 0a9586434a
commit a56f11d68a
1 changed files with 1 additions and 1 deletions

View File

@ -37,7 +37,7 @@ No matter which strategy you choose, it is important to understand that in most
### `DeamonSet` strategy
Kubernetes `DaemonSets` allows you to define workloads that need to be deployed once per node in the cluster. This enables workloads that are running in the same node to communicate with local daprd APIs, no matter where the `Kubernetes Scheduler` schedules your workload.
With Kubernetes `DaemonSet`, you can define workloads that need to be deployed once per node in the cluster. This enables workloads that are running in the same node to communicate with local daprd APIs, no matter where the Kubernetes `Scheduler` schedules your workload.
<img src="/images/dapr-shared/daemonset.png" width=800 style="padding-bottom:15px;">