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

clarification on updating components 

Signed-off-by: yaron2 <schneider.yaron@live.com>
This commit is contained in:
yaron2 2022-03-24 10:30:08 -07:00
parent e8f1423213
commit 875c4b3102
1 changed files with 30 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

30
daprdocs/content/en/operations/components/component-updates.md Normal file
View File

@ -0,0 +1,30 @@
---
type: docs
title: "Component updates"
linkTitle: "Component updates"
weight: 250
description: "Updating components in Kubernetes and self hosted environments"
---
When making an update to an existing component, the Dapr process needs to be restarted in order to pick up the latest version of the components.
Dapr does not update components automatically.
## Kubernetes
When running in Kubernetes, the process of updating a component involves two steps:
1. Applying the new component YAML to the desired namespace
2. Performing a [rollout restart operation](https://kubernetes.io/docs/reference/kubectl/cheatsheet/#updating-resources) on your deployments to pick up the latest component
## Self Hosted
When running in Self Hosted mode, the process of updating a component involves a single step of stopping the `daprd` process and starting it again to pick up the latest component.
## Further reading
- [Components concept]({{< ref components-concept.md >}})
- [Reference secrets in component definitions]({{< ref component-secrets.md >}})
- [Supported state stores]({{< ref supported-state-stores >}})
- [Supported pub/sub brokers]({{< ref supported-pubsub >}})
- [Supported secret stores]({{< ref supported-secret-stores >}})
- [Supported bindings]({{< ref supported-bindings >}})
- [Set component scopes]({{< ref component-scopes.md >}})