From 412ec912b3de0734b820b7b87d6dc87f5a172fab Mon Sep 17 00:00:00 2001 From: Trond Hindenes Date: Fri, 29 Jan 2021 20:41:29 +0100 Subject: [PATCH] Use helm install instead of helm upgrade --install --- .../operations/hosting/kubernetes/kubernetes-production.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/daprdocs/content/en/operations/hosting/kubernetes/kubernetes-production.md b/daprdocs/content/en/operations/hosting/kubernetes/kubernetes-production.md index 83ffd81c0..a0ba34db1 100644 --- a/daprdocs/content/en/operations/hosting/kubernetes/kubernetes-production.md +++ b/daprdocs/content/en/operations/hosting/kubernetes/kubernetes-production.md @@ -63,9 +63,10 @@ You can find information [here]({{< ref "install-dapr-selfhost.md#using-helm-adv When deploying Dapr in a production-ready configuration, it's recommended to deploy with a highly available configuration of the control plane. It is recommended to create a values file instead of specifying parameters on the command-line. This file should be checked in to source control so that you can track changes made to it. - For a full list of all available options you can set in the values file (or by using the `--set` command-line option), see https://github.com/dapr/dapr/blob/master/charts/dapr/README.md. +Instead of using either `helm install` or `helm upgrade` as shown below, you can also run `helm upgrade --install` - this will dynamically determine whether to install or upgrade. + ```bash # add/update the helm repo helm repo add dapr https://dapr.github.io/helm-charts/ @@ -82,7 +83,7 @@ global.ha.enabled: true EOF # run install/upgrade -helm upgrade --install dapr dapr/dapr \ +helm install dapr dapr/dapr \ --version= \ --namespace dapr-system \ --create-namespace \