Why does helm need a cluster-side component (tiller)?

10/11/2018

I understand that helm consists of a client-side component (the helm CLI) and a cluster-side component (tiller). The docs say that tiller is responsible for building and managing releases. But why does this need to be done from the cluster? Why can't helm build and manage releases from the client, and then simply push resources to kubernetes?

-- Alex Flint
kubernetes
kubernetes-helm

2 Answers

10/11/2018

Tiller can also be run on the client side as mentioned in the Helm documentation here. The documentation refers to it as Running Tiller Locally.

But, as mentioned in the same documentation it's mainly for the sake of development. Had been thinking about it and not exactly sure why only for development and not for production.

-- Praveen Sripati
Source: StackOverflow

10/11/2018

There where a lot of limitations with running client side only, as mentioned in this thread https://github.com/helm/helm/issues/2722. But helm v3 will be a complete rewrite with no server side component.

-- TowmeyKaw
Source: StackOverflow