Merge pull request #387 from smothiki/release-v2.2.0

feat(update): update docs to reflect v2.2.0

Author: Sivaram Mothiki

_scripts/deploy.sh

@@ -5,7 +5,7 @@
 
 cd "$(dirname "$0")" || exit 1
 
-export IMAGE_PREFIX=deisci VERSION=v2.1.0
+export IMAGE_PREFIX=deisci VERSION=v2.2.0
 docker login -e="$DOCKER_EMAIL" -u="$DOCKER_USERNAME" -p="$DOCKER_PASSWORD"
 DEIS_REGISTRY='' make -C .. docker-build docker-push
 docker login -e="$QUAY_EMAIL" -u="$QUAY_USERNAME" -p="$QUAY_PASSWORD" quay.io

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-v2.1.0`
+* **Step 3:** If you haven't already fetched the helm classic chart, do so with `helmc fetch deis/workflow-v2.2.0`
 * **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.
@@ -48,14 +48,14 @@ The helm classic chart for Deis Workflow can be easily configured to connect Wor
               * To specify tenant set `SWIFT_TENANT` if the auth version is 2 or more.
 
     * **2.** Using template file `tpl/generate_params.toml`:
-        * Open the helm classic chart with `helmc edit workflow-v2.1.0` and look for the template file `tpl/generate_params.toml`
+        * Open the helm classic chart with `helmc edit workflow-v2.2.0` 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-v2.1.0`
+* **Step 5:** Save your changes and re-generate the helm classic chart by running `helmc generate -x manifests workflow-v2.2.0`
 * **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-v2.1.0` using your desired object storage.
+You are now ready to `helmc install workflow-v2.2.0` using your desired object storage.
 
 ## Object Storage Configuration and Credentials
 

src/installing-workflow/configuring-postgres.md

@@ -31,7 +31,7 @@ $ psql -h <host> -p <port> -d postgres -U <"postgres" or your own username>
 
 The Helm Classic chart for Deis Workflow can be easily configured to connect the Workflow controller component to an off-cluster PostgreSQL database.
 
-* **Step 1:** If you haven't already fetched the Helm Classic chart, do so with `helmc fetch deis/workflow-v2.1.0`
+* **Step 1:** If you haven't already fetched the Helm Classic chart, do so with `helmc fetch deis/workflow-v2.2.0`
 * **Step 2:** Update database connection details either by setting the appropriate environment variables _or_ by modifying the template file `tpl/generate_params.toml`. Note that environment variables take precedence over settings in `tpl/generate_params.toml`.
     * **1.** Using environment variables:
         * Set `DATABASE_LOCATION` to `off-cluster`.
@@ -41,18 +41,18 @@ The Helm Classic chart for Deis Workflow can be easily configured to connect the
         * Set `DATABASE_USERNAME` to the username of the database user that owns the database-- typically `deis`.
         * Set `DATABASE_PASSWORD` to the password for the database user that owns the database.
     * **2.** Using template file `tpl/generate_params.toml`:
-        * Open the Helm Classic chart with `helmc edit workflow-v2.1.0` and look for the template file `tpl/generate_params.toml`
+        * Open the Helm Classic chart with `helmc edit workflow-v2.2.0` and look for the template file `tpl/generate_params.toml`
         * Update the `database_location` parameter to `off-cluster`.
         * Update the values in the `[database]` configuration section to properly reflect all connection details.
         * Save your changes.
     * Note: Whether using environment variables or `tpl/generate_params.toml`, you do not need to (and must not) base64 encode any values, as the Helm Classic chart will automatically handle encoding as necessary.
-* **Step 3:** Re-generate the Helm Classic chart by running `helmc generate -x manifests workflow-v2.1.0`
+* **Step 3:** Re-generate the Helm Classic chart by running `helmc generate -x manifests workflow-v2.2.0`
 * **Step 4:** Check the generated files in your `manifests` directory. You should see:
     * `deis-controller-rc.yaml` contains relevant connection details.
     * `deis-database-secret-creds.yaml` exists and contains base64 encoded database username and password.
     * No other database-related Kubernetes resources are defined. i.e. none of `database-database-service-account.yaml`, `database-database-service.yaml`, or `database-database-rc.yaml` exist.
 
-You are now ready to `helmc install workflow-v2.1.0` [as usual][installing].
+You are now ready to `helmc install workflow-v2.2.0` [as usual][installing].
 
 [database]: ../understanding-workflow/components.md#database
 [object storage]: configuring-object-storage.md

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-v2.1.0            # fetches the chart into a
+$ helmc fetch deis/workflow-v2.2.0            # fetches the chart into a
                                               # local workspace
-$ helmc generate -x manifests workflow-v2.1.0 # generates various secrets
-$ helmc install workflow-v2.1.0               # injects resources into
+$ helmc generate -x manifests workflow-v2.2.0 # generates various secrets
+$ helmc install workflow-v2.2.0               # injects resources into
                                               # your cluster
 ```
 

src/managing-workflow/platform-logging.md

@@ -54,7 +54,7 @@ Error: There are currently no log messages. Please check the following things:
 ## Default Configuration
 By default the Fluentd pod can be configured to talk to numerous syslog endpoints. So for example it is possible to have Fluentd send log messages to both the Logger component and [Papertrail](https://papertrailapp.com/). This allows production deployments of Deis to satisfy stringent logging requirements such as offsite backups of log data.
 
-Configuring Fluentd to talk to multiple syslog endpoints means adding the following stanzas to the [Fluentd daemonset manifest](https://github.com/deis/charts/blob/master/workflow-v2.1.0/tpl/deis-logger-fluentd-daemon.yaml) -
+Configuring Fluentd to talk to multiple syslog endpoints means adding the following stanzas to the [Fluentd daemonset manifest](https://github.com/deis/charts/blob/master/workflow-v2.2.0/tpl/deis-logger-fluentd-daemon.yaml) -
 
 ```
 env:

src/managing-workflow/upgrading-workflow.md

@@ -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-v2.1.0
+$ helmc fetch deis/workflow-v2.2.0
 
 # update your off-cluster storage configuration
-$ $EDITOR $(helmc home)/workspace/charts/workflow-v2.1.0/tpl/generate_params.toml
+$ $EDITOR $(helmc home)/workspace/charts/workflow-v2.2.0/tpl/generate_params.toml
 
 # generate new templates
-$ helmc generate -x manifests workflow-v2.1.0
+$ helmc generate -x manifests workflow-v2.2.0
 
 # copy your active database secrets into the helmc workspace
 $ cp ~/active-deis-database-secret-creds.yaml \
-	$(helmc home)/workspace/charts/workflow-v2.1.0/manifests/deis-database-secret-creds.yaml
+	$(helmc home)/workspace/charts/workflow-v2.2.0/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-v2.1.0/manifests/deis-builder-secret-ssh-private-keys.yaml
+	$(helmc home)/workspace/charts/workflow-v2.2.0/manifests/deis-builder-secret-ssh-private-keys.yaml
 
 # uninstall workflow
-$ helmc uninstall workflow-v2.0.0 -n deis
+$ helmc uninstall workflow-v2.1.0 -n deis
 
-# install workflow v2.1.0
-$ helmc install workflow-v2.1.0
+# install workflow v2.2.0
+$ helmc install workflow-v2.2.0
 ```
 
 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-v2.1.0            # fetches the chart into a
+$ helmc fetch deis/workflow-v2.2.0            # fetches the chart into a
                                               # local workspace
-$ helmc generate -x manifests workflow-v2.1.0 # generates various secrets
-$ helmc install workflow-v2.1.0               # injects resources into
+$ helmc generate -x manifests workflow-v2.2.0 # generates various secrets
+$ helmc install workflow-v2.2.0               # 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-v2.1.0            # fetches the chart into a
+$ helmc fetch deis/workflow-v2.2.0            # fetches the chart into a
                                               # local workspace
-$ helmc generate -x manifests workflow-v2.1.0 # generates various secrets
-$ helmc install workflow-v2.1.0               # injects resources into
+$ helmc generate -x manifests workflow-v2.2.0 # generates various secrets
+$ helmc install workflow-v2.2.0               # 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-v2.1.0            # fetches the chart into a
+$ helmc fetch deis/workflow-v2.2.0            # fetches the chart into a
                                               # local workspace
-$ helmc generate -x manifests workflow-v2.1.0 # generates various secrets
-$ helmc install workflow-v2.1.0               # injects resources into
+$ helmc generate -x manifests workflow-v2.2.0 # generates various secrets
+$ helmc install workflow-v2.2.0               # injects resources into
                                               # your cluster
 ```
 

src/roadmap/release-checklist.md

@@ -243,9 +243,9 @@ You are now done with the release.
 # Step 12: Bump Client and Server Versions to the Next Development Version
 
 After finishing the release, you'll now need to advance the client and server versions to the next
-targeted release. For example, if `v2.1.0` was just cut and the next release on the roadmap is
-`v2.2.0`, make a PR to bump the [client][client-platform-version] and
-[server][server-platform-version] versions to `v2.2.0-dev`.
+targeted release. For example, if `v2.2.0` was just cut and the next release on the roadmap is
+`v2.3.0`, make a PR to bump the [client][client-platform-version] and
+[server][server-platform-version] versions to `v2.3.0-dev`.
 
 
 [client-platform-version]: https://github.com/deis/workflow-cli/blob/master/version/version.go#L4