From 875c4b3102e13e3a84ab6968cd3d2c07c2daf3b3 Mon Sep 17 00:00:00 2001 From: yaron2 Date: Thu, 24 Mar 2022 10:30:08 -0700 Subject: [PATCH] clarification on updating components Signed-off-by: yaron2 --- .../components/component-updates.md | 30 +++++++++++++++++++ 1 file changed, 30 insertions(+) create mode 100644 daprdocs/content/en/operations/components/component-updates.md diff --git a/daprdocs/content/en/operations/components/component-updates.md b/daprdocs/content/en/operations/components/component-updates.md new file mode 100644 index 000000000..b218826ab --- /dev/null +++ b/daprdocs/content/en/operations/components/component-updates.md @@ -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 >}})