From b8b81f5e3511cd6765024243eb3b5a30d3ddee7f Mon Sep 17 00:00:00 2001 From: Zsolt Kulcsar Date: Wed, 27 Mar 2019 14:45:12 +0000 Subject: [PATCH] Signed-off-by: Zsolt Kulcsar Adding gotchaes section to reflect on issue #4331 --- docs/helm/helm_upgrade.md | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) diff --git a/docs/helm/helm_upgrade.md b/docs/helm/helm_upgrade.md index 676c26595..3a38dc190 100644 --- a/docs/helm/helm_upgrade.md +++ b/docs/helm/helm_upgrade.md @@ -62,6 +62,27 @@ which results in "pwd: 3jk$o2z=f\30with'quote". helm upgrade [RELEASE] [CHART] [flags] ``` +### Gotchas + +#### --install + +When issuing the helm update command one can specify the `-` / `--install` flag what will install a new release as per the parameters provided. The expectation is that a new release is being created in the namespace passed as paramater. However. As the releases in helm 2 are globally scoped install can have some unintented sideeffects. + +*If there is a release deployed already with the given name in any namespaces; the already existing release will be updated irrespective to the namespace parameter.* + +Example: + +``` +helm upgrade --install product --namespace development helm-charts/product-2.0.0 + +WARNING: Namespace "development" doesn't match with previous. Release will be deployed to production +Release "product" has been upgraded. Happy Helming! +``` + +To avoid the above it is advised that: +* don't use the `--install` flag as the above behaviour can't be turned of in helm 2 +* make sure that release names are unique (applying namespace to the name of the release for example) + ### Options ```