Updating components

Updating deployed components used by applications

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.

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 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
• Reference secrets in component definitions
• Supported state stores
• Supported pub/sub brokers
• Supported secret stores
• Supported bindings
• Set component scopes

Last modified June 19, 2023: Merge pull request #3565 from dapr/aacrawfi/skip-secrets-close (b1763bf)