Skip to content
Helm Tiller images for amd64, arm64, and armhf. βš“οΈπŸŽ‰
Shell JavaScript Dockerfile
Branch: master
Clone or download
semantic-release-bot chore(release): 1.1.1 [skip ci]
## [1.1.1](v1.1.0...v1.1.1) (2019-09-18)

### Bug Fixes

* **ci:** Fix curl. ([bd11042](bd11042))
Latest commit 5fe0a02 Sep 18, 2019
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.circleci fix(ci): Fix curl. Sep 18, 2019
assets
manifests ref(docs): Update README. Mar 7, 2019
scripts fix(ci): Fix curl. Sep 18, 2019
.dockerignore fix(build): Use new `build-cross` makefile target. (#5) Feb 25, 2019
Dockerfile fix(deps): Upgrade image deps. (#7) Aug 7, 2019
README.md ref(docs): Update README. Mar 7, 2019
package.json chore(release): 1.1.1 [skip ci] Sep 18, 2019
release.config.js feat(ci): Add semantic-release setup. May 13, 2019
yarn.lock fix(deps): Upgrade image deps. (#7) Aug 7, 2019

README.md

Tiller Multiarch

Sailing the seas of orchestration on any device you'd like.

CircleCI Docker Pulls

Nightly builds of Kubernetes Helm's tiller service as a multiarch Docker image. Using the Docker Image Manifest V2 API, we're able to support the three most common architectures with a single image:

  • amd64 (most PCs / cloud providers)
  • 64-bit ARM (stylized as either arm64 or aarch64, although there are subtle differences) This includes the majority of modern SBCs, including:
  • 32-bit ARM, armhf / armv7 / arm6l (older Raspberry Pi boards, Odroid XU4)

As mentioned above, images are built compliant with v2.2 of the Docker manifest API. No need to specify separate images for different architectures (particularly annoying if you have an architecturally heterogeneous cluster); the Docker client infers for you which image to pull.


Usage / deployment

Creating the tiller deployment with this image is as simple as running helm init and overriding the --tiller-image flag, i.e.:

$ helm init --tiller-image=jessestuart/tiller

Note that depending on your version of Kubernetes and your RBAC configuration, you'll likely need to create and specify a ServiceAccount as well, e.g.:

$ kubectl apply -f manifests/tiller-rbac.yaml
$ helm init --tiller-image=jessestuart/tiller --service-account tiller
You can’t perform that action at this time.