The documentation you are viewing is for Dapr v1.10 which is an older version of Dapr. For up-to-date documentation, see the latest version.
When making an update to an existing deployed component used by an application, Dapr does not update the component automatically. The Dapr sidecar needs to be restarted in order to pick up the latest version of the component. How this done depends on the hosting environment.
When running in Kubernetes, the process of updating a component involves two steps:
- Applying the new component YAML to the desired namespace
- Performing a rollout restart operation on your deployments to pick up the latest component
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.
- Components concept
- Reference secrets in component definitions
- Supported state stores
- Supported pub/sub brokers
- Supported secret stores
- Supported bindings
- Set component scopes
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.