Drop Helm v2 support (#613)

Resolves #589

Signed-off-by: xiaomudk <xiaomudk@gmail.com>

docs/index.md

@@ -178,8 +178,6 @@ lockFilePath: path/to/lock.file
 # In other words, unset values results in no flags passed to helm.
 # See the helm usage (helm SUBCOMMAND -h) for more info on default values when those flags aren't provided.
 helmDefaults:
-  tillerNamespace: tiller-namespace  #dedicated default key for tiller-namespace
-  tillerless: false                  #dedicated default key for tillerless
   kubeContext: kube-context          #dedicated default key for kube-context (--kube-context)
   cleanupOnFail: false               #dedicated default key for helm flag --cleanup-on-fail
   # additional and global args passed to helm (default "")
@@ -289,10 +287,6 @@ releases:
     atomic: true
     # when true, cleans up any new resources created during a failed release (default false)
     cleanupOnFail: false
-    # name of the tiller namespace (default "")
-    tillerNamespace: vault
-    # if true, will use the helm-tiller plugin (default false)
-    tillerless: false
     # enable TLS for request to Tiller (default false)
     tls: true
     # path to TLS CA certificate file (default "$HELM_HOME/ca.pem")
@@ -1008,13 +1002,6 @@ environments:
       - http://$HOSTNAME/artifactory/example-repo-local/test.tgz@environments/production.secret.yaml
 ```
 
-## Tillerless
-
-With the [helm-tiller](https://github.com/rimusz/helm-tiller) plugin installed, you can work without tiller installed.
-
-To enable this mode, you need to define `tillerless: true` and set the `tillerNamespace` in the `helmDefaults` section
-or in the `releases` entries.
-
 ## DAG-aware installation/deletion ordering with `needs`
 
 `needs` controls the order of the installation/deletion of the release:

docs/writing-helmfile.md

@@ -112,8 +112,8 @@ releases:
 
 Release Templating supports the following parts of release definition:
 - basic fields: `name`, `namespace`, `chart`, `version`
-- boolean fields: `installed`, `wait`, `waitForJobs`, `tillerless`, `verify` by the means of additional text
-  fields designed for templating only: `installedTemplate`, `waitTemplate`, `tillerlessTemplate`, `verifyTemplate`
+- boolean fields: `installed`, `wait`, `waitForJobs`, `verify` by the means of additional text
+  fields designed for templating only: `installedTemplate`, `waitTemplate`, `verifyTemplate`
   ```yaml
   # ...
     installedTemplate: '{{`{{ eq .Release.Namespace "kube-system" }}`}}'
@@ -328,7 +328,6 @@ Where the gotmpl file loaded in the second part looks like:
 
 ```yaml
 helmDefaults:
-  tillerNamespace: kube-system
   kubeContext: {{ .Values.kubeContext }}
   verify: false
   {{ if .Values.wait }}
@@ -347,7 +346,6 @@ So in `mydefaults.yaml.gotmpl`, both `.Values.kubeContext` and `.Values.wait` ar
 
 ```yaml
 helmDefaults:
-  tillerNamespace: kube-system
   kubeContext: test
   verify: false
   wait: false