Skip to content

installing-deis-workflow.md

Latest commit

 

History

History
80 lines (57 loc) · 3.05 KB

installing-deis-workflow.md

File metadata and controls

80 lines (57 loc) · 3.05 KB

Installing Deis Workflow

We will use the Helm package manager for Kubernetes to install Deis Workflow onto a Kubernetes cluster. If you don't have Helm installed, see Helm's own documentation for more info.

Check Your Setup

First check that you have helm installed and the version is correct.

$ helm --version
0.4.0

Ensure your kubectl client is installed and ensure it can connect to your Kubernetes cluster. This is where Helm will attempt to communicate with the cluster. You can test that it is working properly by running:

$ helm target
Kubernetes master is running at https://10.245.1.2
Heapster is running at https://10.245.1.2/api/v1/proxy/namespaces/kube-system/services/heapster
KubeDNS is running at https://10.245.1.2/api/v1/proxy/namespaces/kube-system/services/kube-dns
KubeUI is running at https://10.245.1.2/api/v1/proxy/namespaces/kube-system/services/kube-ui
Grafana is running at https://10.245.1.2/api/v1/proxy/namespaces/kube-system/services/monitoring-grafana
InfluxDB is running at https://10.245.1.2/api/v1/proxy/namespaces/kube-system/services/monitoring-influxdb

If you see a list of targets like the one above, 'helm' can communicate with the kubernetes master.

Add the Deis Chart Repository

The Deis Chart Repository contains everything you need to install Deis onto your Kubernetes cluster, with a single helm install command.

Run the following command to add this repository to Helm:

$ helm repo add deis https://github.com/deis/charts

Install Deis Workflow

Now that you have Helm installed and have added the Deis Chart Repository, install Workflow by running:

$ helm fetch deis/workflow-beta2             # fetches the chart into a
                                             # local workspace
$ helm generate -x manifests workflow-beta2  # generates various secrets
$ helm install workflow-beta2                # injects resources into
                                             # your cluster

Helm will install a variety of Kubernetes resources in the deis namespace. You'll need to wait for the pods that it launched to be ready. Monitor their status by running:

$ kubectl get pods --namespace=deis

If you would like kubectl to automatically update as the pod states change, run (type Ctrl-C to stop the watch):

$ kubectl get pods --namespace=deis -w

Once you see all of the pods in the READY state, Deis Workflow is up and running!

Configure your Load Balancer

After installing Workflow on your cluster, you'll need to configure your load balancer. Following this step is especially important on AWS because the default idle timeout for connections on the Elastic Load Balancer is too low for the Builder to finish a git push operation.

Next, configure dns so you can register your first user.