Update to latest method of deploying tiller

[yorinasub17]

Recently, we updated terraform-kubernetes-helm to provide a module for the actual deployment of Tiller (https://github.com/gruntwork-io/terraform-kubernetes-helm/releases/tag/v0.3.0) that uses the kubernetes_deployment resource of the kubernetes provider, as opposed to using kubergrunt. In this model, kubergrunt is used to manage the TLS certificates, but not the deployment of Tiller itself. This has a few advantages:

• We still get to keep the main reason we use kubergrunt: securely managing the TLS certificates so that they don't leak into Terraform state.
• The steps are broken up in Terraform, which leads to better error handling when something goes wrong. Before, any failure in the command will mess up the deployment and recovery was difficult because the command was not idempotent. (See notes in slack about why it was difficult to make the deploy command itself idempotent).
• This leads to better composability/flexibility. Our users can now pick and choose which features to use, including avoiding kubergrunt altogether by either hand generating certs, or using the tls provider.
• Now you can upgrade and adjust the tiller deployment in Terraform. E.g rolling out a new version can be done by updating a variable and applying the Terraform code.

The main disadvantage of this approach is that there is more code to copy from the example, because it is more broken up. There is more work to be done to address this, but I think this is sufficient for now.

[autero1]

When will kubergrunt be open sourced?

[yorinasub17]

Ok going to merge this.