From d9f56b9137f05ef44716bec4900cc27ff87cf4a9 Mon Sep 17 00:00:00 2001 From: Joao C Costa Date: Wed, 4 Jan 2023 01:13:24 +0000 Subject: [PATCH] Corrected rendering of exports (#3035) Signed-off-by: Joao C Costa Signed-off-by: Joao C Costa Co-authored-by: greenie-msft <56556602+greenie-msft@users.noreply.github.com> --- .../en/operations/hosting/kubernetes/kubernetes-deploy.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/daprdocs/content/en/operations/hosting/kubernetes/kubernetes-deploy.md b/daprdocs/content/en/operations/hosting/kubernetes/kubernetes-deploy.md index fb860a9de16..26744722726 100644 --- a/daprdocs/content/en/operations/hosting/kubernetes/kubernetes-deploy.md +++ b/daprdocs/content/en/operations/hosting/kubernetes/kubernetes-deploy.md @@ -64,9 +64,11 @@ There are some scenarios where it's necessary to install Dapr from a private Hel - having a custom Dapr deployment - pulling Helm charts from trusted registries that are managed and maintained by your organization +``` export DAPR_HELM_REPO_URL="https://helm.custom-domain.com/dapr/dapr" export DAPR_HELM_REPO_USERNAME="username_xxx" export DAPR_HELM_REPO_PASSWORD="passwd_xxx" +``` Setting the above parameters will allow `dapr init -k` to install Dapr images from the configured Helm repository.