ref(helm): update the docs to refer helm classic instead of helm

Author: Keerthan Mala

CONTRIBUTING.md

@@ -22,7 +22,7 @@ Our official support channels are:
   - controller: https://github.com/deis/controller/issues
   - database: https://github.com/deis/postgres/issues
   - documentation: https://github.com/deis/workflow/issues
-  - helm: https://github.com/helm/helm/issues
+  - helm classic: https://github.com/helm/helm/issues
   - minio: https://github.com/deis/minio/issues
   - registry: https://github.com/deis/registry/issues
   - router: https://github.com/deis/router/issues

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

@@ -11,25 +11,25 @@ Every component that relies on object storage uses two inputs for configuration:
 1. Component-specific environment variables (e.g. `BUILDER_STORAGE` and `REGISTRY_STORAGE`)
 2. Access credentials stored as a Kubernetes secret named `objectstorage-keyfile`
 
-The helm chart for Deis Workflow can be easily configured to connect Workflow components to off-cluster object storage. Deis Workflow currently supports Google Compute Storage, Amazon S3 and Azure Blob Storage.
+The helm classic chart for Deis Workflow can be easily configured to connect Workflow components to off-cluster object storage. Deis Workflow currently supports Google Compute Storage, Amazon S3 and Azure Blob Storage.
 
 * **Step 1:** Create storage buckets for each of the Workflow subsystems: builder, registry and database
     * 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 chart, do so with `helm fetch deis/workflow-beta3`
-* **Step 4:** Open the helm chart with `helm edit workflow-beta3` and look for the template file `tpl/generate_params.toml`
+* **Step 3:** If you haven't already fetched the helm classic chart, do so with `helmc fetch deis/workflow-beta3`
+* **Step 4:** Open the helm classic chart with `helmc edit workflow-beta3` and look for the template file `tpl/generate_params.toml`
 * **Step 5:** Update the `storage` parameter to reference the storage platform you are using: `s3`, `azure`, `gcs`
 * **Step 6:** 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 will handle encoding automatically
-* **Step 7:** Save your changes and re-generate the helm chart by running `helm generate -x manifests workflow-beta3`
+    * Note: you do not need to base64 encode any of these values as Helm Classic will handle encoding automatically
+* **Step 7:** Save your changes and re-generate the helm classic chart by running `helmc generate -x manifests workflow-beta3`
 * **Step 8:** Check the generated file in your manifests directory, you should see `deis-objectstorage-secret.yaml`
 
-You are now ready to `helm install workflow-beta3` using your desired object storage.
+You are now ready to `helmc install workflow-beta3` using your desired object storage.
 
 ## Object Storage Configuration and Credentials
 
-During the `helm generate` step, Helm creates a Kubernetes secret in the Deis namespace named `objectstorage-keyfile`. The exact structure of the file depends on storage backend specified in `tpl/generate_params.toml`.
+During the `helmc generate` step, Helm Classic creates a Kubernetes secret in the Deis namespace named `objectstorage-keyfile`. The exact structure of the file depends on storage backend specified in `tpl/generate_params.toml`.
 
 ```
 # Set the storage backend

src/installing-workflow/installing-deis-workflow.md

@@ -1,21 +1,21 @@
 # Installing Deis Workflow
 
-We will use the Helm package manager for Kubernetes to install Deis Workflow onto a Kubernetes cluster. If you don't have Helm installed, see [Helm's own documentation][helm] for more info.
+We will use the Helm Classic package manager for Kubernetes to install Deis Workflow onto a Kubernetes cluster. If you don't have Helm Classic installed, see [Helm Classic's own documentation][helm] for more info.
 
 ## Check Your Setup
 
-First check that the `helm` command is available and the version is 0.6 or newer.
+First check that the `helmc` command is available and the version is 0.6 or newer.
 
 ```
-$ helm --version
-helm version 0.6.0+1c8688e
+$ helmc --version
+helmc version 0.6.0+1c8688e
 ```
 
-Ensure the `kubectl` client is installed and can connect to your Kubernetes cluster. `helm` will
+Ensure the `kubectl` client is installed and can connect to your Kubernetes cluster. `helmc` will
 use it to communicate. You can test that it is working properly by running:
 
 ```
-$ helm target
+$ helmc target
 Kubernetes master is running at https://10.245.1.2
 Heapster is running at https://10.245.1.2/api/v1/proxy/namespaces/kube-system/services/heapster
 KubeDNS is running at https://10.245.1.2/api/v1/proxy/namespaces/kube-system/services/kube-dns
@@ -24,7 +24,7 @@ Grafana is running at https://10.245.1.2/api/v1/proxy/namespaces/kube-system/ser
 InfluxDB is running at https://10.245.1.2/api/v1/proxy/namespaces/kube-system/services/monitoring-influxdb
 ```
 
-If you see a list of targets like the one above, `helm` can communicate with the Kubernetes master.
+If you see a list of targets like the one above, `helmc` can communicate with the Kubernetes master.
 
 Deis Workflow requires Kubernetes 1.2 or higher. You can test that by running:
 
@@ -37,27 +37,27 @@ Server Version: version.Info{Major:"1", Minor:"2", GitVersion:"v1.2.3", GitCommi
 ## Add the Deis Chart Repository
 
 The [Deis Chart Repository](https://github.com/deis/charts) contains everything you
-need to install Deis onto your Kubernetes cluster, with a single `helm install` command.
+need to install Deis onto your Kubernetes cluster, with a single `helmc install` command.
 
-Run the following command to add this repository to Helm:
+Run the following command to add this repository to Helm Classic:
 
 ```
-$ helm repo add deis https://github.com/deis/charts
+$ helmc repo add deis https://github.com/deis/charts
 ```
 
 ## Install Deis Workflow
 
-Now that you have Helm installed and have added the Deis Chart Repository, install Workflow by running:
+Now that you have Helm Classic installed and have added the Deis Chart Repository, install Workflow by running:
 
 ```
-$ helm fetch deis/workflow-beta3             # fetches the chart into a
+$ helmc fetch deis/workflow-beta3             # fetches the chart into a
                                              # local workspace
-$ helm generate -x manifests workflow-beta3  # generates various secrets
-$ helm install workflow-beta3                # injects resources into
+$ helmc generate -x manifests workflow-beta3  # generates various secrets
+$ helmc install workflow-beta3                # injects resources into
                                              # your cluster
 ```
 
-Helm will install a variety of Kubernetes resources in the `deis` namespace.
+Helm Classic will install a variety of Kubernetes resources in the `deis` namespace.
 You'll need to wait for the pods that it launched to be ready. Monitor their status
 by running:
 

src/managing-workflow/upgrading-workflow.md

@@ -3,9 +3,9 @@
 To upgrade to a newer version of Workflow, run the following:
 
 ```
-$ helm uninstall workflow-beta2 -n deis
-$ helm update
-$ helm fetch deis/workflow-beta3
-$ helm generate -x manifests workflow-beta3
-$ helm install workflow-beta3
+$ helmc uninstall workflow-beta2 -n deis
+$ helmc update
+$ helmc fetch deis/workflow-beta3
+$ helmc generate -x manifests workflow-beta3
+$ helmc install workflow-beta3
 ```

src/roadmap/release-checklist.md

@@ -30,7 +30,7 @@ A release consists of the following artifacts:
   - [workflow-e2e](https://github.com/deis/workflow-e2e)
   - [workflow-manager](https://github.com/deis/workflow-manager)
   - [workflow-cli](https://github.com/deis/workflow-cli)
-2. A new [Helm chart for Deis](https://github.com/deis/charts) that references all of the new
+2. A new [Helm Classic chart for Deis](https://github.com/deis/charts) that references all of the new
 images referenced above. For example, if `$DEIS_RELEASE` is `2.0.0-beta3`, the new chart would
 be in a new directory called `workflow-beta3`.
 
@@ -54,9 +54,9 @@ git submodule status
 
 Keep the list of commit SHAs handy - you'll need it for later.
 
-# Step 2: Create a new Helm chart
+# Step 2: Create a new Helm Classic chart
 
-Next, we'll create a new [Helm](https://github.com/helm/helm) chart so that we can "stage" a
+Next, we'll create a new [Helm Classic](https://github.com/helm/helm) chart so that we can "stage" a
 version of our release for testing. The process is fairly simple:
 
 1. Create a new branch: `git checkout -b release-$DEIS_RELEASE`
@@ -105,14 +105,14 @@ and run the following two commands to tag and push updated docker images:
 TAG=$DEIS_RELEASE make docker-tag docker-push
 ```
 
-# Step 5: Update Helm chart
+# Step 5: Update Helm Classic chart
 
-Now that new Docker images are on public Docker repositories, it's time to update the Helm chart
+Now that new Docker images are on public Docker repositories, it's time to update the Helm Classic chart
 to reference the official images. To do so, simply modify all `dockerTag` entries in the
 `generate_params.toml` files in the `workflow-$DEIS_RELEASE_SHORT` and
 `workflow-$DEIS_RELEASE_SHORT-e2e` to be `$DEIS_RELEASE` (instead of the ones based on git tags).
 
-Also, ensure that the `README.md` and `Chart.yaml` files in the new helm chart have updated references to the chart. For example, references to `helm install workflow-betaX` should become `helm install workflow-$DEIS_RELEASE_SHORT`
+Also, ensure that the `README.md` and `Chart.yaml` files in the new helm classic chart have updated references to the chart. For example, references to `helmc install workflow-betaX` should become `helmc install workflow-$DEIS_RELEASE_SHORT`
 
 If you find any references that should be bumped, open a pull-request against the documentation.
 
@@ -123,7 +123,7 @@ When you're done, commit and push your changes. You should get your pull request
 # Step 6: Update Changelogs
 
 At this point, part of the first part and all of the second part of the release is complete.
-That is, the Helm chart for the new Deis version is done, and new Docker versions for all
+That is, the Helm Classic chart for the new Deis version is done, and new Docker versions for all
 components are done.
 
 The remaining work is simply generating changelogs and tagging each component's GitHub repository.

src/understanding-workflow/architecture.md

@@ -8,7 +8,7 @@ compliant Kubernetes cluster.
 
 ![System Overview](../diagrams/Ecosystem_Basic.png)
 
-Operators use [Helm][] to configure and install the Workflow components which
+Operators use [Helm Classic][helm] to configure and install the Workflow components which
 interface directly with the underlying Kubernetes cluster. Service discovery,
 container availability and networking are all delegated to Kubernetes, while
 Workflow provides a clean and simple developer experience.

src/understanding-workflow/concepts.md

@@ -28,7 +28,7 @@ directly from application source code, aggregating logs, and managing deployment
 configurations and app releases are just some of the features Workflow adds.
 
 Deis Workflow is a set of Kubernetes-native components, installable via
-[Helm][helm]. Systems engineers who are familiar with Kubernetes will feel right
+[Helm Classic][helm]. Systems engineers who are familiar with Kubernetes will feel right
 at home running Workflow.
 
 See the [components][components] overview for more detail.