Deploying helm-tiller template
Deploy helm-tiller template on existing IBM Cloud Kubernetes Service cluster.
Procedure
- Log in to IBM Cloud: https://console.bluemix.net/containers-kubernetes/clusters.
- Create a cluster and wait until the cluster is in ready state.
- Log in to Cloud Automation Manager user interface.
- Create IBM Cloud Kuberneters service connection and connect to the deployed IBM Cloud Kubernetes Service cluster. For the actual steps, see Configuring IBM Cloud Kubernetes Service.
-
Retrieve the IBM Cloud Kubernetes Service cluster and Auth info for the helm-tiller template deployment.
- Go to https://console.bluemix.net/containers-kubernetes/clusters.
- Follow all the steps there to configure IBM Cloud Kubernetes Service cluster access by using CLI.
-
Run the export command to export an API key and then log in to bluemix through CLI.
export BLUEMIX_API_KEY=<Bluemix Api Key>The output of
ibmcloud cs cluster-config <cluster name>gives the location of your cluster configuration files. For example:export KUBECONFIG=/home/developer/.bluemix/plugins/container-service/clusters/<cluster name>/<tiller yml file> -
Go to folder that contains the configuration file. For example:
cd /home/developer/.bluemix/plugins/container-service/clusters/<cluster name>There are two files in this folder.
For example:
ca-dal13-jeff-iks-tiller.pem kube-config-dal13-jeff-iks-tiller.yml -
In Mac OS, open the following configuration files
base64 xxxxxxx.yml > config base64 xxxxx.pem > authIn Unix/Linux, open the follwoing configuration files:
base64 -w 0 xxxxxx.yml > config base64 -w 0 xxxxxx.pem > authWhen you deploy helm tiller template from starterlibrary, do the following steps:
- Enter the contents of config file in the Cluster configuration field
- Enter the contents of auth file in the Cluster certificate authority field
-
Submit deploy and ensure that the deployment completes successfully:
Run the following command to verify whether the tiller is installed on IBM Cloud Kubernetes Service cluster that is located in the same environment as your configured IBM Cloud Kubernetes Service cluster:
kubectl get pods -n kube-system -l app=helmExample output:
NAME READY STATUS RESTARTS AGE tiller-deploy-6cddf6cc56-8hk22 1/1 Running 0 22h