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 

Signed-off-by: Mark Fussell <markfussell@gmail.com>
Signed-off-by: salaboy <Salaboy@gmail.com>
This commit is contained in:
Mark Fussell 2024-06-26 13:04:54 -07:00 committed by salaboy
parent 872d8c79a1
commit 6fc2e274fd
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

@ -27,7 +27,7 @@ By default, when Dapr is installed into a Kubernetes cluster, the Dapr control p
<img src="/images/dapr-shared/sidecar.png" width=800 style="padding-bottom:15px;">
While sidecars are Dapr's default deployment strategy, some use cases require other approaches. Let's say you want to decouple the lifecycle of your workloads from the Dapr APIs. A typical example of this is functions, or function-as-a-service runtimes, which might automatically downscale your idle workloads to free up resources. For such cases, keeping the Dapr APIs and all the Dapr async functionalities (such as subscriptions) separate might be required.
While sidecars are Dapr's default deployment, some use cases require other approaches. Let's say you want to decouple the lifecycle of your workloads from the Dapr APIs. A typical example of this is functions, or function-as-a-service runtimes, which might automatically downscale your idle workloads to free up resources. For such cases, keeping the Dapr APIs and all the Dapr async functionalities (such as subscriptions) separate might be required.
Dapr Shared was created for these scenarios, extending the Dapr sidecar model with two new deployment approaches: `DaemonSet` and `Deployment`.