<p>Check <a href="https://github.com/helm/helm/issues/3130" rel="nofollow noreferrer">https://github.com/helm/helm/issues/3130</a>, this might help.
I followed the instruction in the post:</p>

<pre><code>kubectl --namespace kube-system create serviceaccount tiller

kubectl create clusterrolebinding tiller --clusterrole cluster-admin --serviceaccount=kube-system:tiller

helm init --service-account tiller --upgrade
</code></pre>

<p>This works for me.</p>

CC BY-SA 4.0
2019-09-19T13:42:45.883Z
2019-09-19T13:42:45.883Z
chenfwww
<p>By default, tiller stores release information in ConfigMaps in the namespace where it is running.</p>

<p>You can refer to the official <a href="https://helm.sh/docs/using_helm/#role-based-access-control" rel="nofollow noreferrer">Helm RBAC documentation</a> for more information on setting up different RBAC scenarios for Tiller.</p>

<p>Kubernetes authorizes API requests using the API server. It evaluates all of the request attributes against all policies and allows or denies the request. All parts of an API request must be allowed by some policy in order to proceed. This means that permissions are denied by default.</p>

<p>For more details see: <a href="https://kubernetes.io/docs/reference/access-authn-authz/authorization/" rel="nofollow noreferrer">kubernetes authorization</a> </p>

CC BY-SA 4.0
2019-08-03T12:02:35.653Z
2019-08-04T08:37:36.620Z
2019-08-04T08:37:36.620Z
Fodil
<p>I installed Kubernetes, helm on the Ubuntu 16.04.6 Box, I want to deploy kubernetes-dashboard using helm but getting below error while installing it</p>

<pre><code>$ helm install stable/kubernetes-dashboard --name dashboard-demo
Error: release dashboard-demo failed: namespaces "default" is forbidden: User "system:serviceaccount:kube-system:default" cannot get resource "namespaces" in API group "" in the namespace "default"

$ helm list
Error: configmaps is forbidden: User "system:serviceaccount:kube-system:default" cannot list resource "configmaps" in API group "" in the namespace "kube-system"
</code></pre>

<p>Tools Version:</p>

<pre><code>$ kubectl version
Client Version: version.Info{Major:"1", Minor:"14", GitVersion:"v1.14.1", GitCommit:"b7394102d6ef778017f2ca4046abbaa23b88c290", GitTreeState:"clean", BuildDate:"2019-04-08T17:11:31Z", GoVersion:"go1.12.1", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"14", GitVersion:"v1.14.1", GitCommit:"b7394102d6ef778017f2ca4046abbaa23b88c290", GitTreeState:"clean", BuildDate:"2019-04-08T17:02:58Z", GoVersion:"go1.12.1", Compiler:"gc", Platform:"linux/amd64"}

$ helm version
Client: &amp;version.Version{SemVer:"v2.13.1", GitCommit:"618447cbf203d147601b4b9bd7f8c37a5d39fbb4", GitTreeState:"clean"}
Server: &amp;version.Version{SemVer:"v2.13.1", GitCommit:"618447cbf203d147601b4b9bd7f8c37a5d39fbb4", GitTreeState:"clean"}

$ kubectl get pods --all-namespaces
NAMESPACE     NAME                                       READY   STATUS             RESTARTS   AGE
kube-system   calico-kube-controllers-58dc446999-zrwz6   1/1     Running            0          4h41m
kube-system   calico-node-wjczq                          1/1     Running            0          4h41m
kube-system   coredns-fb8b8dccf-fp9gx                    1/1     Running            0          4h41m
kube-system   coredns-fb8b8dccf-q574t                    1/1     Running            0          4h41m
kube-system   etcd-ubuntu1                               1/1     Running            1          4h40m
kube-system   kube-apiserver-ubuntu1                     1/1     Running            1          4h40m
kube-system   kube-controller-manager-ubuntu1            1/1     Running            2          4h40m
kube-system   kube-proxy-ztmms                           1/1     Running            1          4h41m
kube-system   kube-scheduler-ubuntu1                     1/1     Running            2          4h41m
kube-system   tiller-deploy-864c6f45bb-2585b             1/1     Running            0          6m55s
</code></pre>

<p>helm updated to latest version.</p>

<p>I followed this : <a href="https://stackoverflow.com/questions/46672523/helm-list-cannot-list-configmaps-in-the-namespace-kube-system">https://stackoverflow.com/questions/46672523/helm-list-cannot-list-configmaps-in-the-namespace-kube-system</a> but still facing same issue, how can we fixed it ?</p>

CC BY-SA 4.0
2019-08-02T11:58:52.477Z
I faced the same issue. Here is the solution: https://www.youtube.com/watch?v=fH1kfQ22qYY
Ashutosh
CC BY-SA 4.0
2019-08-03T06:56:08.263Z
Could you please summarise the solution here as well as link to the longer version in the video? We can't guarantee that the video will be permanently available.
Bruce Becker
<docker><kubernetes><containers><helm>
helm - cannot get resource "namespaces" in API group
Nullpointer
# helm - cannot get resource "namespaces" in API group

(Asked by: username_0 on 2019-05-07)

I installed Kubernetes, helm on the Ubuntu 16.04.6 Box, I want to deploy kubernetes-dashboard using helm but getting below error while installing it
$ helm install stable/kubernetes-dashboard --name dashboard-demo
Error: release dashboard-demo failed: namespaces "default" is forbidden: User "system:serviceaccount:kube-system:default" cannot get resource "namespaces" in API group "" in the namespace "default"

$ helm list
Error: configmaps is forbidden: User "system:serviceaccount:kube-system:default" cannot list resource "configmaps" in API group "" in the namespace "kube-system"

Tools Version:
$ kubectl version
Client Version: version.Info{Major:"1", Minor:"14", GitVersion:"v1.14.1", GitCommit:"b7394102d6ef778017f2ca4046abbaa23b88c290", GitTreeState:"clean", BuildDate:"2019-04-08T17:11:31Z", GoVersion:"go1.12.1", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"14", GitVersion:"v1.14.1", GitCommit:"b7394102d6ef778017f2ca4046abbaa23b88c290", GitTreeState:"clean", BuildDate:"2019-04-08T17:02:58Z", GoVersion:"go1.12.1", Compiler:"gc", Platform:"linux/amd64"}

$ helm version
Client: &version.Version{SemVer:"v2.13.1", GitCommit:"618447cbf203d147601b4b9bd7f8c37a5d39fbb4", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.13.1", GitCommit:"618447cbf203d147601b4b9bd7f8c37a5d39fbb4", GitTreeState:"clean"}

$ kubectl get pods --all-namespaces
NAMESPACE     NAME                                       READY   STATUS             RESTARTS   AGE
kube-system   calico-kube-controllers-58dc446999-zrwz6   1/1     Running            0          4h41m
kube-system   calico-node-wjczq                          1/1     Running            0          4h41m
kube-system   coredns-fb8b8dccf-fp9gx                    1/1     Running            0          4h41m
kube-system   coredns-fb8b8dccf-q574t                    1/1     Running            0          4h41m
kube-system   etcd-ubuntu1                               1/1     Running            1          4h40m
kube-system   kube-apiserver-ubuntu1                     1/1     Running            1          4h40m
kube-system   kube-controller-manager-ubuntu1            1/1     Running            2          4h40m
kube-system   kube-proxy-ztmms                           1/1     Running            1          4h41m
kube-system   kube-scheduler-ubuntu1                     1/1     Running            2          4h41m
kube-system   tiller-deploy-864c6f45bb-2585b             1/1     Running            0          6m55s

helm updated to latest version.
I followed this : https://stackoverflow.com/questions/46672523/helm-list-cannot-list-configmaps-in-the-namespace-kube-system but still facing same issue, how can we fixed it ?

**Tags:** docker, kubernetes, containers, helm

> **Comments:**
> **username_1**: I faced the same issue. Here is the solution: https://www.youtube.com/watch?v=fH1kfQ22qYY  
> **username_2**: Could you please summarise the solution here as well as link to the longer version in the video? We can't guarantee that the video will be permanently available.  

---

## 2 answers

### Answer by username_3 on 2019-09-19. Score: 4

Check https://github.com/helm/helm/issues/3130, this might help.
I followed the instruction in the post:
kubectl --namespace kube-system create serviceaccount tiller

kubectl create clusterrolebinding tiller --clusterrole cluster-admin --serviceaccount=kube-system:tiller

helm init --service-account tiller --upgrade

This works for me.


---

### Answer by username_4 on 2019-08-03. Score: 1

By default, tiller stores release information in ConfigMaps in the namespace where it is running.

You can refer to the official [Helm RBAC documentation](https://helm.sh/docs/using_helm/#role-based-access-control) for more information on setting up different RBAC scenarios for Tiller.

Kubernetes authorizes API requests using the API server. It evaluates all of the request attributes against all policies and allows or denies the request. All parts of an API request must be allowed by some policy in order to proceed. This means that permissions are denied by default.

For more details see: [kubernetes authorization](https://kubernetes.io/docs/reference/access-authn-authz/authorization/)


---

