-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
forbidden: User "system:serviceaccount:kube-system:default" cannot get namespaces in the namespace "default #21
Comments
I had the same issue and followed this link to resolve it. Not sure how much should be added to the documentation as it is strictly Helm and RBAC related issue. |
kubectl patch deploy --namespace kube-system tiller-deploy -p '{"spec":{"template":{"spec":{"serviceAccount":"tiller"}}}}' I am getting below error |
thanks all, I had the same and was able to fix the issue by following the doc https://docs.helm.sh/using_helm/#tiller-and-role-based-access-control |
@postak were you able to resolve the issue with the links mentioned in the thread? |
Yes, with these commands
kubectl create serviceaccount --namespace kube-system tiller
# kubectl create clusterrolebinding tiller-cluster-rule
--clusterrole=cluster-admin --serviceaccount=kube-system:tiller
# kubectl patch deploy --namespace kube-system tiller-deploy -p
'{"spec":{"template":{"spec":{"serviceAccount":"tiller"}}}}'
Il giorno ven 17 ago 2018 alle 19:03 Peter Jausovec <
[email protected]> ha scritto:
@postak <https://github.com/postak> were you able to resolve the issue
with the links mentioned in the thread?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#21 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAnPtsExq6_UPnQZX-ORTtMwHfC1OMqlks5uRvd8gaJpZM4TM9q4>
.
--
-- Sent from my StarTAC
|
Perfect. Since this was resolved and it's not really related to Fn, I'll close it. Feel free to open a new issue if you ran into issues. Thanks! |
Worked here as well, thanks guys |
kubectl patch deploy --namespace kube-system tiller-deploy -p '{"spec":{"template":{"spec":{"serviceAccount":"tiller"}}}}' |
@rnkhouse if the problem you're seeing is related to Fn, please open a separate issue and explain what you're seeing. This issue is closed. |
|
Closing one. Please reopen if necessary or if you see the following problem with the latest chart. |
Try this :
|
Why is this is not part of the Helm documentation?!
|
I had this same issue, you need to escape the double quotes characters on the json: |
I solved running all of these commands in given sequence to my k8s cluster: kubectl create serviceaccount --namespace kube-system tiller And then you can run your helm command like: |
The latest v2.15 HELM is finally compatible with K8s v1.16.2. |
produces
and
produces
I´m running an automanaged cluster on Digital Ocean. Tiller has been installed through the Gitlab Dashboard after connecting to my cluster. Appreciate any help |
|
I had to escape double quotes and also use " instead of '. |
Isn't tiller gone with helm 2? |
@miraj-godha-guavus - Your suggested worked for me. |
Following the instruction in the documentation when running
helm install --name myfn fn
I get the error forbidden: User "system:serviceaccount:kube-system:default" cannot get namespaces in the namespace "default
I solved running these commands to my k8s cluster:
kubectl create serviceaccount --namespace kube-system tiller
kubectl create clusterrolebinding tiller-cluster-rule --clusterrole=cluster-admin --serviceaccount=kube-system:tiller
kubectl patch deploy --namespace kube-system tiller-deploy -p '{"spec":{"template":{"spec":{"serviceAccount":"tiller"}}}}'
if confirmed should be added to the documentation
The text was updated successfully, but these errors were encountered: