jessestuart/tiller-multiarch

Helm Tiller images for amd64, arm64, and armhf. ⚓️🎉

Tiller Multiarch

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

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:
  • Most Raspberry Pi boards,
  • Pine64 Rock64 / RockPro64 / Pine64
  • Hardkernel's Odroid C2
  • Libre Computer's roc-rk3328-cc "Renegade"
• 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

tiller-multiarch's Issues

Helm template for integer conversion doesn't work

Can we update the sprig version ?
For example, {{ $valint := (int .Values.zookeeper.replicaCount) }} doesn't work.

Proposal: merge these changes into the official Helm repository

This project is great, but it would be also be great if it wasn't needed, and it wouldn't be needed if the official Tiller build had these changes merged in for multiarch.

As requested here:

• "Release new tiller docker image on arm64", helm/helm#3269
• "Meta: Build system changes" helm/helm#1968

Creating this issue to make an easy cross-reference.

Missing Tiller v2.10.0 ?

There is a new version of Helm v2.10.0 and the Docker image is of Tiller exist v2.10.0

Do you plan to build this image ?

The automated release is failing 🚨

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

---

Invalid npm token.

The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org.

If you are using Two-Factor Authentication, make configure the auth-only level is supported. semantic-release cannot publish with the default auth-and-writes level.

Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.

---

Good luck with your project ✨

Your semantic-release bot 📦🚀

Cluster networking not working

Thanks for supplying this image :-)

I am getting this issue:
helm/helm#6227 - I've left a full description in there and thought I'd ask here also.

I've tried v2.11.0, v2.9.0 and v2.15.0 with timeouts each time

It looks like the latest version of the image having problems with arm64

the old version,still working

[root@node155 images]# docker history c757e38a7f04 --no-trunc
IMAGE                                                                     CREATED             CREATED BY                                                                                                                            SIZE                COMMENT
sha256:c757e38a7f040c4b83ddda9e20b3f00a8072d66b5b509d69934af0873cb367d8   16 months ago       /bin/sh -c #(nop)  ENTRYPOINT ["/tiller"]                                                                                             0 B
<missing>                                                                 16 months ago       /bin/sh -c #(nop)  USER [nobody]                                                                                                      0 B
<missing>                                                                 16 months ago       /bin/sh -c #(nop)  EXPOSE 44134/tcp                                                                                                   0 B
<missing>                                                                 16 months ago       /bin/sh -c #(nop) COPY file:8fada10522675f7b8aad7b82fc84a87c9b79bd77a3f927c3d415ae11aafac420 in /tiller                               30.3 MB
<missing>                                                                 16 months ago       /bin/sh -c #(nop) COPY file:b2b36cac1f7d7128c7bd8630127aa6e2927e92d7bcfaa97848f34dd5bc464d3c in /etc/ssl/certs/ca-certificates.crt    237 kB
<missing>                                                                 16 months ago       /bin/sh -c #(nop)  LABEL maintainer=Jesse Stuart <[email protected]>                                                                 0 B
<missing>                                                                 18 months ago       /bin/sh -c #(nop)  CMD ["/bin/sh"]                                                                                                    0 B
<missing>                                                                 18 months ago       /bin/sh -c #(nop) COPY file:0f1d36dd7d8d53613b275660a88c5bf9b608ea8aa73a8054cb8bdbd73fd971ac in /etc/localtime                        127 B
<missing>                                                                 18 months ago       /bin/sh -c #(nop) ADD file:a4b53e2a2e207c5107a76c16d91b99cb1ed4ecb90b363913798e663426137d45 in /                                      4.2 MB

the latest version

[root@node155 images]# docker history 516584798bd4 --no-trunc
IMAGE                                                                     CREATED             CREATED BY                                                                                                                            SIZE                COMMENT
sha256:516584798bd494740b76bbab496b63889409f7f13a28dc20a112aaea414ecb43   28 hours ago        /bin/sh -c #(nop)  ENTRYPOINT ["/tiller"]                                                                                             0 B
<missing>                                                                 28 hours ago        /bin/sh -c #(nop)  USER [nobody]                                                                                                      0 B
<missing>                                                                 28 hours ago        /bin/sh -c #(nop)  EXPOSE 44134/tcp                                                                                                   0 B
<missing>                                                                 28 hours ago        /bin/sh -c #(nop) COPY file:091d2a65366d205fc0db557b2f495da40adb5a33c9d656d02c3ea08bb22f6c4d in /etc/ssl/certs/ca-certificates.crt    233 kB
<missing>                                                                 28 hours ago        /bin/sh -c #(nop) COPY file:882825d8c8c2f18cabe0b918d009a39a718733dc31b7aefb7ea5d26eda08387c in /tiller                               41.1 MB
<missing>                                                                 28 hours ago        /bin/sh -c #(nop) COPY file:e7c78df7f700aa7919a4c290870a3ae9661cbeafbc90dfc8fa77a329498dbfd5 in /helm                                 40.5 MB
<missing>                                                                 28 hours ago        /bin/sh -c #(nop)  ENV HOME=/tmp                                                                                                      0 B
<missing>                                                                 28 hours ago        /bin/sh -c #(nop)  LABEL maintainer=Jesse Stuart <[email protected]>                                                                 0 B
<missing>                                                                 6 weeks ago         /bin/sh -c #(nop)  CMD ["/bin/sh"]                                                                                                    0 B
<missing>                                                                 6 weeks ago         /bin/sh -c #(nop) ADD file:d48cac34fac385cbc1de6adfdd88300f76f9bbe346cd17e64fd834d042a98326 in /                                      5.55 MB


[root@node155 helm]# kubectl logs -f tiller-deploy-58c947c456-t6v4b -n kube-system
standard_init_linux.go:178: exec user process caused "exec format error"

What's the difference between the two versions

Add a License to this repository

Hello!

Thanks a lot for your great work here, I've noticed that there isn't a license to this repository.
By default if you don't have a license, then all rights are reserved and it is not Open Source or Free. You cannot modify or redistribute this code without explicit permission from the copyright holder.

See the following links explaining this a bit more:

• https://choosealicense.com/no-permission/
• https://help.github.com/en/github/building-a-strong-community/adding-a-license-to-a-repository
• https://opensource.stackexchange.com/questions/1720/what-can-i-assume-if-a-publicly-published-project-has-no-license

Redistributing under Apache2 is pretty traditional in the cloud native space and might be what you can look into:

• https://github.com/helm/helm/blob/master/LICENSE
• https://github.com/kubernetes/kubernetes/blob/master/LICENSE

TLDR legal does a good job at explaining that license: https://tldrlegal.com/license/apache-license-2.0-(apache-2.0)

You should use any license you want, just having clarification on how you are distributing this software a good enough resolution of this issue :)
Thanks again!

can you build image of arm64-v2.15.2

title