dapr
/
docs
mirror of https://github.com/dapr/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

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-02 14:50:19 +01:00
parent da6ec97c0e
commit ce0d6b8d6f
1 changed files with 2 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
daprdocs/content/en/operations/dapr-shared/dapr-shared.md
View File

@ -11,7 +11,8 @@ By default, Dapr automatically injects a sidecar to enable the Dapr APIs for you
Dapr Shared enables different deployment strategies to create Dapr applications using Kubernetes `Daemonset` or `Deployment`.
By running daprd as a Kubernetes `DaemonSet` resource, the daprd container will be running in each Kubernetes Node, reducing the network hops between the applications and Dapr. You can also choose to run Dapr Shared as a Kubernetes `Deployment`, in which case, the Kubernetes scheduler will decide in which node the Dapr Shared instance will run.
- **`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.
{{% alert title="Dapr Shared deployments" color="primary" %}}
For each Dapr Application, you need to deploy the Dapr Shared chart using different `shared.appId`s.