Skip to content

install-gke.md

Latest commit

 

History

History
85 lines (64 loc) · 3.42 KB

install-gke.md

File metadata and controls

85 lines (64 loc) · 3.42 KB

Install Deis Workflow on Google Compute Engine

Check Your Setup

First check that the helm command is available and the version is 0.8 or newer.

$ helmc --version
helmc version 0.8.0+f3cafbc

Ensure the kubectl client is installed and can connect to your Kubernetes cluster. helm will use it to communicate. You can test that it is working properly by running:

$ helmc target
Kubernetes master is running at https://104.154.234.246
GLBCDefaultBackend is running at https://104.154.234.246/api/v1/proxy/namespaces/kube-system/services/default-http-backend
Heapster is running at https://104.154.234.246/api/v1/proxy/namespaces/kube-system/services/heapster
KubeDNS is running at https://104.154.234.246/api/v1/proxy/namespaces/kube-system/services/kube-dns
kubernetes-dashboard is running at https://104.154.234.246/api/v1/proxy/namespaces/kube-system/services/kubernetes-dashboard

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 helmc install command.

Run the following command to add this repository to Helm:

$ helmc 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:

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

Helm Classic 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 --namespace=deis get pods

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

$ kubectl --namespace=deis get pods -w

Depending on the order in which the Workflow components initialize, some pods may restart. This is common during the installation: if a component's dependencies are not yet available, that component will exit and Kubernetes will automatically restart it.

Here, you can see that controller, builder and registry all took a few loops before there were able to start:

$ kubectl --namespace=deis get pods
NAME                          READY     STATUS    RESTARTS   AGE
deis-builder-miekp            1/1       Running   1          2m
deis-controller-egu7x         1/1       Running   3          2m
deis-database-ok3ev           1/1       Running   0          2m
deis-logger-fluentd-d5cb9     1/1       Running   0          2m
deis-logger-fluentd-u6azj     1/1       Running   0          2m
deis-logger-rf3z9             1/1       Running   0          2m
deis-minio-sdfyz              1/1       Running   0          2m
deis-registry-f534k           1/1       Running   4          2m
deis-router-t3qb2             1/1       Running   0          2m
deis-workflow-manager-kbpw3   1/1       Running   0          2m

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

Next, configure dns so you can register your first user and deploy an application.