Merge pull request #259 from mboersma/upgrade-docs

docs(upgrading-workflow): describe "keeper" upgrade behavior

Author: mboersma

src/installing-workflow/index.md

@@ -11,11 +11,11 @@ You need to [install Helm Classic and Deis Workflow CLI before continuing](../qu
 
 ## Check Your Setup
 
-Check that the `helmc` command is available and the version is 0.7 or newer.
+Check that the `helmc` command is available and the version is 0.8 or newer.
 
 ```
 $ helmc --version
-helmc version 0.7.0+20a7ed7
+helmc version 0.8.0+f3cafbc
 ```
 
 Ensure the `kubectl` client is installed and can connect to your Kubernetes cluster. `helmc` uses `kubectl` to interact

src/managing-workflow/upgrading-workflow.md

@@ -9,3 +9,28 @@ $ helmc fetch deis/workflow-beta4
 $ helmc generate -x manifests workflow-beta4
 $ helmc install workflow-beta4
 ```
+
+## Keeping Essential Pieces
+
+!!! note
+    "Keeper" upgrade behavior requires Helm Classic 0.8.0 or newer and the workflow-rc1
+    or workflow-dev chart.
+
+Helm Classic recognizes when a manifest inside a chart is marked as a "keeper" and will leave
+it alone during `helmc uninstall`.
+
+The Workflow Chart marks the "deis" Kubernetes `Namespace` and the `Service` for the registry
+and for the router as keepers. This keeps the external `LoadBalancer` intact so that routing
+and DNS are preserved while reinstalling Workflow.
+
+To remove Workflow completely from a Kubernetes cluster, run the following:
+
+```
+$ helmc uninstall -n deis -y workflow-dev
+$ kubectl delete ns deis  # Be sure you want to delete the
+                          # Namespace and all its contents!
+```
+
+See the Helm Classic documentation for more detail about [keeper manifests].
+
+[keeper manifests]: http://helm-classic.readthedocs.io/en/latest/awesome/#keeper-manifests

src/quickstart/install-cli-tools.md

@@ -35,9 +35,9 @@ Install the latest `helmc` cli for Linux or Mac OS X with:
 Check your work by running `helmc version`:
 
     $ helmc version
-    helmc version 0.7.0+20a7ed7
+    helmc version 0.8.0+f3cafbc
 
-Make sure you are running at least version 0.7.0 or newer.
+Make sure you are running at least version 0.8.0 or newer.
 
 ## Step 2: Boot a Kubernetes Cluster and Install Deis Workflow
 

src/quickstart/provider/aws/install-aws.md

@@ -2,11 +2,11 @@
 
 ## Check Your Setup
 
-First check that the `helmc` command is available and the version is 0.7 or newer.
+First check that the `helmc` command is available and the version is 0.8 or newer.
 
 ```
 $ helmc --version
-helmc version 0.7.0+20a7ed7
+helmc version 0.8.0+f3cafbc
 ```
 
 Ensure the `kubectl` client is installed and can connect to your Kubernetes cluster. `helmc` will

src/quickstart/provider/gke/install-gke.md

@@ -2,11 +2,11 @@
 
 ## Check Your Setup
 
-First check that the `helm` command is available and the version is 0.7 or newer.
+First check that the `helm` command is available and the version is 0.8 or newer.
 
 ```
 $ helmc --version
-helmc version 0.7.0+20a7ed7
+helmc version 0.8.0+f3cafbc
 ```
 
 Ensure the `kubectl` client is installed and can connect to your Kubernetes cluster. `helm` will

src/quickstart/provider/vagrant/install-vagrant.md

@@ -2,11 +2,11 @@
 
 ## Check Your Setup
 
-First check that the `helm` command is available and the version is 0.7 or newer.
+First check that the `helm` command is available and the version is 0.8 or newer.
 
 ```
 $ helmc --version
-helmc version 0.7.0+20a7ed7
+helmc version 0.8.0+f3cafbc
 ```
 
 Ensure the `kubectl` client is installed and can connect to your Kubernetes cluster. `helm` will