dapr
/
docs
mirror of https://github.com/dapr/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
docs/daprdocs/content/en/operations/components/component-updates.md

1.3 KiB
Raw Blame History

type title linkTitle weight description
docs Component updates Component updates 250 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 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 >}})