Get support for sagikazarmark/terraform-tiller

If you're new to LTH, please see our FAQ for more information on what it is we do.

Support Options

Unfortunately, there are currently no active helpers for this repository on the platform. Until they become available, we reccomend the following actions:

View Open Issues

Take a look to see if anyone else has experienced the same issue as you and if they managed to solve it.

Open an Issue

Make sure to read any relevant guidelines for opening issues on this repo before posting a new issue.

Sponsor directly

Check out the page and see if there are any options to sponsor this project or it's developers directly.

sagikazarmark/terraform-tiller

Tiller Terraform Module

CircleCI

Install Tiller on a Kubernetes cluster using Terraform.

Installation / Usage

  1. Configure a kubernetes provider in the parent module
  2. Add the following snippet to your terraform config:
module "tiller" {
  source  = "github.com/sagikazarmark/terraform-tiller"
  version = "~> 0.1.0"
}

Configuration

Name Default Description
rbac_enabled false Whether to create role-based access control resources (service account and cluster role binding).
tiller_namespace kube-system The Kubernetes namespace to use to deploy Tiller.
tiller_service_account tiller The Kubernetes service account to add to Tiller.
tiller_replicas 1 The amount of Tiller instances to run on the cluster.
tiller_image gcr.io/kubernetes-helm/tiller The image used to install Tiller.
tiller_version v2.11.0 The Tiller image version to install.
tiller_max_history 0 (unlimited) Limit the maximum number of revisions saved per release. Use 0 for no limit.
tiller_net_host empty Install Tiller with net=host.
tiller_node_selector empty Determine which nodes Tiller can land on.

Initial Chart installation

You might want to preinstall your servers with Kubernetes plugins such as unsupported ingress controllers, right after Tiller is installed. Since Terraform still doesn't support depends_on feature on modules, such as this one, there's manual work that needs to be done. This is an example how you can make sure Helm Chart installation starts after the Tiller service is ready:

module "tiller" {
  ...
}

resource "null_resource" "install_voyager" {
  provisioner "local-exec" {
    command     = "./helm/voyager.sh ${local_file.kube_cluster_yaml.filename}"
    interpreter = ["bash", "-c"]
  }
}
#!/usr/bin/env bash

wait_for_tiller () {
	KUBECONFIG=$1 kubectl --namespace kube-system get pods \
		--field-selector=status.phase==Running | grep 'tiller-deploy' \
		| grep '1/1' \
		> /dev/null 2>&1
}

until wait_for_tiller $1; do
	echo "Waiting for tiller-deploy to get ready..."
	sleep 5
done

echo "Installing Voyager Ingress..."

helm repo add appscode https://charts.appscode.com/stable --kubeconfig $CWD/../kube_config_cluster.yml
helm repo update --kubeconfig $CWD/../kube_config_cluster.yml

helm install appscode/voyager --name voyager-operator --version 8.0.1 \
	--namespace kube-system --set cloudProvider=baremetal \
	--kubeconfig $1 > /dev/null 2>&1

echo "Voyager Ingress installed!"

Why

After a rather long development and review period Terraform accepted a Helm provider as an official plugin. It provides an option to automatically install Tiller on a cluster if necessary, but unfortunately it's a bit buggy and it usually comes with an older Helm/Tiller version (at the time of this writing the included version is 2.9.0 while the latest is 2.12.0). So I created this terraform module to install Tiller separately from the Helm provider.

License

The MIT License (MIT). Please see License File for more information.

Our Mission

We want to make open source more sustainable. The entire platform was born from this and everything we do is in aid of this.

Interesting Articles

Thank you for checking out LiveTechHelper |
2025 © lth-dev incorporated

p-e622a1a2