helm tiller does not existed since Helm 3 - unix1998/technical_notes GitHub Wiki

Helm originally had a component called Tiller, which acted as a server-side component managing Helm releases in a Kubernetes cluster. However, with Helm 3, Tiller was removed due to security concerns and to simplify the architecture.

In Helm 3, there is no Tiller component. Instead, Helm interacts directly with the Kubernetes API server. Here's how Helm 3 works without Tiller:

1. Helm CLI: The Helm command-line interface (CLI) is used to manage charts, releases, and repositories. It communicates directly with the Kubernetes API server.

2. Kubernetes API Server: Helm uses the API server to install, update, and roll back applications (represented as Helm charts) in the cluster. The API server handles all the necessary permissions and security.

3. Releases: When you perform actions like helm install or helm rollback, Helm creates, updates, or deletes Kubernetes resources by sending requests to the Kubernetes API server. There is no need for a persistent server-side component like Tiller.

So, in summary, Helm 3 does not have Tiller. It operates purely as a client-side tool, using the Kubernetes API server for managing applications. This design simplifies security and reduces the complexity of Helm's architecture.