* <chart>.tgz  will now be downloaded to "$HELM_HOME/cache/archive" directory

Fixes https://github.com/kubernetes/helm/issues/2142

* Added archive location to helm init

Improve 'helm create'

docs: Fix typo in command line

ref(tiller): cleanup goimports

Added "tpl" template function

ref(tiller): refactor out cobra from tiller

ref(helm): mix bag of syntax cleanup in cmd/helm

feat(helm): support array index format for --set.

* Use versioned API types from the client-go library

Wherever possible, use the k8s.io/client-go/kubernetes.Interface type
in favor of the client-related types from package

  k8s.io/kubernetes/pkg/client/clientset_generated/internalclientset

The latter are still required by the kubectl "reaper" types used in
the "installer" and "kube" packages.

* Accept the default deployment replica count of one

Don't bother requesting a single replica explicitly.

This adds support for specifying list position with an array index using
`--set`. For example, this now works: `--set servers[0].port=8080`

fix(tiller): track hooks in multi-def manifests

docs(helm): add armada to the additional tools readme

chore(ci): bump go 1.8.3

(docs) - add best practices for running tiller in namespaces

Rename index.md to README.md

fix(tests): Fixes broken unit test

fix(helm): helm home print to stdout

docs(chart_template_guide): remove discussion of blocks

cobra prints to stderr by default

First alias would be dependency rename

The new unit test was not passing an explict subcommand arg to the
root command in the unit test.

Allow updating chart dependencies when packaging a chart

There are a lot of weird edge cases when using blocks inside of charts,
and we have been telling users to avoid using them for the last six
months. This just removes the documentation about them. It also adds a
warning about why blocks should not be used.

fix(helm): Ensures tiller pod lands on a linux node

fix(tiller): make GetReleaseContent return any release

fix(helm): remove unnecessary values merge in processImportValues

Without a node selector to ensure that tiller deploys on a linux node,
the tiller pod can have issues starting in a mixed cluster.

Fixes #2420

fix(helm): modify `helm repo update` help info