Question
Namespaces is forbidden (Helm install on public wordpress chart)
- Posted on November 22, 2018
- Kubernetes
Asked by nicholasrobertm
Hi there! I’ve started out with the hosted Kubernetes and have ran into a bump.
When trying to do a helm install:
helm install --namespace kube-public --name wordpress stable/wordpress
After first setting up the kube cluster I get back an unexpected error
helm install --namespace wordpress --name wordpress stable/wordpress
Error: release wordpress failed: namespaces "wordpress" is forbidden: User "system:serviceaccount:kube-system:default" cannot get resource "namespaces" in API group "" in the namespace "wordpress"
Has anyone seen this before? Is tiller not properly setup?
Thanks for your help!
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Become a contributor for community
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
DigitalOcean Documentation
Full documentation for every DigitalOcean product.
Resources for startups and SMBs
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
Get our newsletter
Stay up to date by signing up for DigitalOcean’s Infrastructure as a Newsletter.
New accounts only. By submitting your email you agree to our Privacy Policy
The developer cloud
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Get started for free
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.
Figured this out, for those who run into it.
This is because by default RBAC is enabled, which prevents tiller from working. To fix this you need to follow these steps: https://docs.bitnami.com/kubernetes/how-to/configure-rbac-in-your-kubernetes-cluster/#use-case-2-enable-helm-in-your-cluster
Which will then allow tiller to do things in the cluster!