Skip to content
This repository has been archived by the owner on Jun 26, 2020. It is now read-only.

Commit

Permalink
Update docs to pin K8s at v1.5.1 and remove helm pull workaround
Browse files Browse the repository at this point in the history
ATT-Comdev do not currently have an image with rbd for K8s 1.5.2, so
until we can move to our own images we should pin the version of K8s at 1.5.1

Also remove workaround for pulling images from gcr.io with docker-engine.
See: moby/moby#30083

This commit should not be merged until this is resolved in Halcyon.
See: att-comdev/halcyon-kubernetes#42

Change-Id: I85c7aa7ba6067ac53013f373dda08b3fac06625d
  • Loading branch information
intlabs committed Jan 25, 2017
1 parent 03f23e3 commit b9fc241
Showing 1 changed file with 2 additions and 23 deletions.
25 changes: 2 additions & 23 deletions doc/source/development-environment.rst
Expand Up @@ -270,7 +270,7 @@ under use.
.. code-block:: console
export KOLLA_HELM_VERSION=2.1.3
export KOLLA_KUBERNETES_VERSION=1.5.2
export KOLLA_KUBERNETES_VERSION=1.5.1
.. end
Expand Down Expand Up @@ -445,28 +445,7 @@ To test that helm is working you can run the following:
helm init --client-only
helm repo update
helm install stable/memcached --name helm-test
.. end
Tiller, which is Helm's server container for starting helm charts, doesn't
work correctly as of January 21st, 2017 with docker-engine-1.13.0. The root
cause and resolution is being tracked in this ssue tracker:
https://github.com/kubernetes/helm/issues/1838. The Kolla community
recommends using the following workaround:

.. path .
.. code-block:: console
kubectl delete --namespace=kube-system deploy tiller-deploy
helm init --tiller-image docker.io/port/tiller:v2.1.3

.. end
After waiting for the tiller image to be pulled to the kubernetes cluster:

.. path .
.. code-block:: console
# check the deployment has succeded
helm ls
# and to check via kubectl
kubectl get all
Expand Down

0 comments on commit b9fc241

Please sign in to comment.