During Installation of Helm3 stable, i found Helm3 stable does not implement tiller deployment for fetching cluster details, it works as a Client utility only, my question is it, if it is not implementing tiller concept for fetching details, how does it connect with EKS.

I have already installed kubectl and it is running fine, is it something like this, helm client is dependent on kubectl service?

I performed following steps: 1.helm version version.BuildInfo{Version:"v3.1.0", GitCommit:"b29d20baf09943e134c2fa5e1e1cab3bf93315fa", GitTreeState:"clean", GoVersion:"go1.13.7"}

2.kubectl create serviceaccount tiller --namespace kube-system serviceaccount/tiller created

3.notepad rbac-config.yaml

4.kubectl apply -f rbac-config.yaml clusterrolebinding.rbac.authorization.k8s.io/tiller-role-binding created

5.helm init --service-account tiller Error: unknown flag: --service-account

I know steps 2,3,4 are not required in Helm3, but curious to know how helm3 interacts as a client service with EKS cluster.