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/hosting/kubernetes/kubernetes-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-06-25 17:48:27 +01:00
parent 6426417b62
commit 7f3e902478
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
daprdocs/content/en/operations/hosting/kubernetes/kubernetes-dapr-shared.md
View File

@ -32,7 +32,7 @@ While sidecars are Dapr's default deployment strategy, some use cases require ot
Dapr Shared was created for these scenarios, extending the Dapr sidecar model with two new deployment approaches: `DaemonSet` and `Deployment`.
{{% alert title="Important" color="primary" %}}
No matter which strategy you choose, it is important to understand that in most use cases, you have one instance of Dapr Shared (Helm release) per service (app-id). This means that if you have an application composed of three microservices, each service is recommended to have its own Dapr Shared instance. Try the `hello kubernetes` with Dapr Shared tutorial linked at the bottom of this page.
No matter which strategy you choose, it is important to understand that in most use cases, you have one instance of Dapr Shared (Helm release) per service (app-id). This means that if you have an application composed of three microservices, each service is recommended to have its own Dapr Shared instance. You can see this in action by trying the [Hello Kubernetes with Dapr Shared tutorial](https://github.com/dapr/dapr-shared/blob/main/docs/tutorial/README.md).
{{% /alert %}}