From d19b6cdd6673b503f98db9be8312632ce151b43e Mon Sep 17 00:00:00 2001 From: Tao Zhou Date: Sat, 4 Feb 2017 17:50:21 +0800 Subject: [PATCH 1/2] docs(install): add doc to use `helm reset` to delete tiller deployment --- docs/install.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) mode change 100644 => 100755 docs/install.md diff --git a/docs/install.md b/docs/install.md old mode 100644 new mode 100755 index 7486904d0..b935fa4f8 --- a/docs/install.md +++ b/docs/install.md @@ -189,7 +189,7 @@ Setting `TILLER_TAG=canary` will get the latest snapshot of master. Because Tiller stores its data in Kubernetes ConfigMaps, you can safely delete and re-install Tiller without worrying about losing any data. The recommended way of deleting Tiller is with `kubectl delete deployment -tiller-deploy --namespace kube-system` +tiller-deploy --namespace kube-system`, or more concisely `helm reset`. Tiller can then be re-installed from the client with: From f745c9c761a23230497da8ce15daa9def1c14ded Mon Sep 17 00:00:00 2001 From: Tao Zhou Date: Tue, 7 Feb 2017 08:09:10 +0800 Subject: [PATCH 2/2] docs(using_helm): fix outdated `helm rollback` example usage in doc Closes #1921 --- docs/using_helm.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) mode change 100644 => 100755 docs/using_helm.md diff --git a/docs/using_helm.md b/docs/using_helm.md old mode 100644 new mode 100755 index 27ea04adb..2ecbee0b6 --- a/docs/using_helm.md +++ b/docs/using_helm.md @@ -324,16 +324,17 @@ cluster. And as we can see above, it shows that our new values from `panda.yaml` were deployed to the cluster. Now, if something does not go as planned during a release, it is easy to -roll back to a previous release. +roll back to a previous release using `helm rollback [RELEASE] [REVISION]`. ```console -$ helm rollback happy-panda --version 1 +$ helm rollback happy-panda 1 ``` The above rolls back our happy-panda to its very first release version. A release version is an incremental revision. Every time an install, upgrade, or rollback happens, the revision number is incremented by 1. -The first revision number is always 1. +The first revision number is always 1. And we can use `helm history [RELEASE]` +to see revision numbers for a certain release. ## Helpful Options for Install/Upgrade/Rollback There are several other helpful options you can specify for customizing the