<pre><code>helm install --name my-rabbitserver stable/rabbitmq --namespace rabbit

Error: release my-rabbitserver failed: namespaces &quot;rabbit&quot; is forbidden: User &quot;system:serviceaccount:kube-system:default&quot; cannot get resource &quot;namespaces&quot; in API group &quot;&quot; in the namespace &quot;rabbit&quot;
</code></pre>
<p>I have tried with (and without a rabbit namespace created before the install attempt)
I am using helm 2.16.9, so I need to qualify the name of my installation with a <code>--name</code></p>
<p>I am using this against a Google Cloud kubernetes cluster</p>

user2129049
<p>It looks as though the Helm tiller pod did not have sufficient priveldeges.
I found this similar issue:
<a href="https://support.sumologic.com/hc/en-us/articles/360037704393-Kubernetes-Helm-install-fails-with-Error-namespaces-sumologic-is-forbidden-User-system-serviceaccount-kube-system-default-cannot-get-resource-namespaces-in-API-group-in-the-namespace-sumologic-" rel="nofollow noreferrer">https://support.sumologic.com/hc/en-us/articles/360037704393-Kubernetes-Helm-install-fails-with-Error-namespaces-sumologic-is-forbidden-User-system-serviceaccount-kube-system-default-cannot-get-resource-namespaces-in-API-group-in-the-namespace-sumologic-</a></p>
<p>Basically I have to stop the tiller deployment, set up tiller ServiceAccount yaml and run it to give tiller access to the kube-system. And then execute helm init again with the new service account.
The helm rabbitmq installs then appear work as advertised</p>
<p>I thought helm was supposed to make life easier, but it still has its own limitations and additional yaml files to get it to work as advertised.</p>
