Prior to Helm 3, it was possible to associate a service account in helm initialization via
helm init --service-account tillerBut since helm init is now deprecated, how can we find out which service account is the Helm associated with?
Helm 3 will have the same permissions according to your system environment variable $KUBECONFIG which defaults to ~/.kube/config or using the following options
--kube-context string name of the kubeconfig context to use
--kubeconfig string path to the kubeconfig fileWith Tiller gone, the security model for Helm is radically simplified. Helm 3 now supports all the modern security, identity, and authorization features of modern Kubernetes. Helm’s permissions are evaluated using your
kubeconfigfile. Cluster administrators can restrict user permissions at whatever granularity they see fit. — Changes since Helm 2: Removal of Tiller