Merge pull request #287 from deis/release-v2.0.0-rc2

chore(workflow-rc2): releasing workflow-rc2

Author: krancour

src/installing-workflow/configuring-object-storage.md

@@ -17,7 +17,7 @@ The helm classic chart for Deis Workflow can be easily configured to connect Wor
     * Note: Depending on your chosen object storage you may need to provide globally unique bucket names.
     * Note: If you provide credentials with sufficient access to the underlying storage, Workflow components will create the buckets if they do not exist.
 * **Step 2:** If applicable, generate credentials that have write access to the storage buckets created in Step 1
-* **Step 3:** If you haven't already fetched the helm classic chart, do so with `helmc fetch deis/workflow-rc1`
+* **Step 3:** If you haven't already fetched the helm classic chart, do so with `helmc fetch deis/workflow-rc2`
 * **Step 4:** Update storage details either by setting the appropriate environment variables or by modifying the template file `tpl/generate_params.toml`
     * **1.** Using environment variables:
         * Set `STORAGE_TYPE` to `s3`, `azure` or `gcs`, then set the following environment variables accordingly.
@@ -40,14 +40,14 @@ The helm classic chart for Deis Workflow can be easily configured to connect Wor
             ```
 
     * **2.** Using template file `tpl/generate_params.toml`:
-        * Open the helm classic chart with `helmc edit workflow-rc1` and look for the template file `tpl/generate_params.toml`
+        * Open the helm classic chart with `helmc edit workflow-rc2` and look for the template file `tpl/generate_params.toml`
         * Update the `storage` parameter to reference the storage platform you are using: `s3`, `azure`, `gcs`
         * Update the values in the section which corresponds to your storage type, including region, bucket names and access credentials
     * Note: you do not need to base64 encode any of these values as Helm Classic will handle encoding automatically
-* **Step 5:** Save your changes and re-generate the helm classic chart by running `helmc generate -x manifests workflow-rc1`
+* **Step 5:** Save your changes and re-generate the helm classic chart by running `helmc generate -x manifests workflow-rc2`
 * **Step 6:** Check the generated file in your manifests directory, you should see `deis-objectstorage-secret.yaml`
 
-You are now ready to `helmc install workflow-rc1` using your desired object storage.
+You are now ready to `helmc install workflow-rc2` using your desired object storage.
 
 ## Object Storage Configuration and Credentials
 

src/installing-workflow/index.md

@@ -54,10 +54,10 @@ $ helmc repo add deis https://github.com/deis/charts
 Now that you have Helm Classic installed and have added the Deis Chart Repository, install Workflow by running:
 
 ```
-$ helmc fetch deis/workflow-rc1             # fetches the chart into a
+$ helmc fetch deis/workflow-rc2             # fetches the chart into a
                                               # local workspace
-$ helmc generate -x manifests workflow-rc1  # generates various secrets
-$ helmc install workflow-rc1                # injects resources into
+$ helmc generate -x manifests workflow-rc2  # generates various secrets
+$ helmc install workflow-rc2                # injects resources into
                                               # your cluster
 ```
 

src/managing-workflow/component-configuration.md

@@ -5,8 +5,8 @@ or service. Helm is heavily influenced by [Homebrew](http://brew.sh/), including
 [formula model](https://github.com/Homebrew/homebrew-core). A Helm chart is to Helm as a Formula
 is to Homebrew.
 
-When you run `helmc fetch deis/workflow-rc1`, you can customize the chart with
-`helmc edit workflow-rc1`. To customize the respective component, edit
+When you run `helmc fetch deis/workflow-rc2`, you can customize the chart with
+`helmc edit workflow-rc2`. To customize the respective component, edit
 `manifests/deis-<component>-rc.yaml` and modify the `env` section of the component to tune these
 settings.
 

src/managing-workflow/upgrading-workflow.md

@@ -19,7 +19,7 @@ See [Configuring Object Storage][] to learn how to store your Workflow data off-
 
 !!! note
     "Keeper" upgrade behavior requires Helm Classic 0.8.0 or newer and the workflow-rc1
-    or workflow-dev chart.
+    or newer chart.
 
 Helm Classic recognizes when a manifest inside a chart is marked as a "keeper"
 and will not uninstall the annotated resource during `helmc uninstall`.
@@ -67,27 +67,27 @@ $ kubectl --namespace=deis get secret database-creds -o yaml > ~/active-deis-dat
 $ kubectl --namespace=deis get secret builder-ssh-private-keys -o yaml > ~/active-deis-builder-secret-ssh-private-keys.yaml
 
 # fetch new chart
-$ helmc fetch deis/workflow-rc1
+$ helmc fetch deis/workflow-rc2
 
 # update your off-cluster storage configuration
-$ $EDITOR $(helmc home)/workspace/charts/workflow-beta4/tpl/generate_params.toml
+$ $EDITOR $(helmc home)/workspace/charts/workflow-rc2/tpl/generate_params.toml
 
 # generate new templates
-$ helmc generate -x manifests workflow-rc1
+$ helmc generate -x manifests workflow-rc2
 
 # copy your active database secrets into the helmc workspace
 $ cp ~/active-deis-database-secret-creds.yaml \
-	$(helmc home)/workspace/charts/workflow-rc1-manifests/deis-database-secret-creds.yaml
+	$(helmc home)/workspace/charts/workflow-rc2-manifests/deis-database-secret-creds.yaml
 
 # copy your active builder ssh keys into the helmc workspace
 $ cp ~/active-deis-builder-secret-ssh-private-keys.yaml \
-	$(helmc home)/workspace/charts/workflow-rc1/manifests/deis-builder-secret-ssh-private-keys.yaml
+	$(helmc home)/workspace/charts/workflow-rc2/manifests/deis-builder-secret-ssh-private-keys.yaml
 
 # uninstall workflow
-$ helmc uninstall workflow-beta4 -n deis
+$ helmc uninstall workflow-rc1 -n deis
 
-# install workflow rc1
-$ helmc install workflow-rc1
+# install workflow rc2
+$ helmc install workflow-rc2
 ```
 
 Make sure to copy the existing `deis-database-secret-creds.yaml` manifest into the new chart

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

@@ -42,10 +42,10 @@ $ helmc repo add deis https://github.com/deis/charts
 Now that you have Helm Classic installed and have added the Deis Chart Repository, install Workflow by running:
 
 ```
-$ helmc fetch deis/workflow-rc1             # fetches the chart into a
+$ helmc fetch deis/workflow-rc2             # fetches the chart into a
                                               # local workspace
-$ helmc generate -x manifests workflow-rc1  # generates various secrets
-$ helmc install workflow-rc1                # injects resources into
+$ helmc generate -x manifests workflow-rc2  # generates various secrets
+$ helmc install workflow-rc2                # injects resources into
                                               # your cluster
 ```
 

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

@@ -40,10 +40,10 @@ $ helmc repo add deis https://github.com/deis/charts
 Now that you have Helm installed and have added the Deis Chart Repository, install Workflow by running:
 
 ```
-$ helmc fetch deis/workflow-rc1             # fetches the chart into a
+$ helmc fetch deis/workflow-rc2             # fetches the chart into a
                                               # local workspace
-$ helmc generate -x manifests workflow-rc1  # generates various secrets
-$ helmc install workflow-rc1                # injects resources into
+$ helmc generate -x manifests workflow-rc2  # generates various secrets
+$ helmc install workflow-rc2                # injects resources into
                                               # your cluster
 ```
 

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

@@ -40,10 +40,10 @@ $ helmc repo add deis https://github.com/deis/charts
 Now that you have Helm installed and have added the Deis Chart Repository, install Workflow by running:
 
 ```
-$ helmc fetch deis/workflow-rc1             # fetches the chart into a
+$ helmc fetch deis/workflow-rc2             # fetches the chart into a
                                               # local workspace
-$ helmc generate -x manifests workflow-rc1  # generates various secrets
-$ helmc install workflow-rc1                # injects resources into
+$ helmc generate -x manifests workflow-rc2  # generates various secrets
+$ helmc install workflow-rc2                # injects resources into
                                               # your cluster
 ```
 

src/roadmap/release-checklist.md

@@ -7,8 +7,8 @@ The below sections present a step-by-step guide to publish a new Workflow releas
 of the examples, we'll be assuming that the below two environment variables are present in wherever
 you're working. Make sure to set them (e.g. by `export`ing them) before you get started.
 
-- `$WORKFLOW_RELEASE` - the full name of this version. For example, `v2.0.0-rc1`
-- `$WORKFLOW_RELEASE_SHORT` - The short name of this version. For example, `rc1`
+- `$WORKFLOW_RELEASE` - the full name of this version. For example, `v2.0.0-rc2`
+- `$WORKFLOW_RELEASE_SHORT` - The short name of this version. For example, `rc2`
 
 # What's a Release?
 
@@ -33,8 +33,8 @@ A release consists of the following artifacts:
   - [workflow-manager](https://github.com/deis/workflow-manager)
   - [workflow-cli](https://github.com/deis/workflow-cli)
 2. A new [Helm Classic chart for Workflow](https://github.com/deis/charts) that references all of the new
-images referenced above. For example, if `$WORKFLOW_RELEASE` is `2.0.0-rc1`, the new chart would
-be in a new directory called `workflow-rc1`.
+images referenced above. For example, if `$WORKFLOW_RELEASE` is `2.0.0-rc2`, the new chart would
+be in a new directory called `workflow-rc2`.
 
 # Step 1: Cut repo branches and push image tags
 
@@ -124,7 +124,7 @@ Also, note there may be an occurrence of the previous oldest release (prior to `
 # Step 5: Manual Testing
 
 After the chart is created with the immutable Docker image tags that represent the final images
-(i.e. the ones that will be re-tagged to the immutable release tag, such as `2.0.0-rc1`), it
+(i.e. the ones that will be re-tagged to the immutable release tag, such as `2.0.0-rc2`), it
 should be manually tested by as many people as possible. Special attention should be paid to the
 user experience, both from an operator and developer perspective.
 

src/troubleshooting/kubectl.md

@@ -4,7 +4,7 @@ This document describes how one can use `kubectl` to debug any issues with the c
 
 ## Diving into the Components
 
-Using `kubectl`, one can inspect the cluster's current state. When `helmc install workflow-rc1`
+Using `kubectl`, one can inspect the cluster's current state. When `helmc install workflow-rc2`
 is invoked, Workflow is installed into the `deis` namespace. To inspect if Workflow is running,
 run: