Skip to content
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

Issue with nginx-ingress-gke #421

Closed
MarkEdmondson1234 opened this issue Apr 25, 2018 · 7 comments
Closed

Issue with nginx-ingress-gke #421

MarkEdmondson1234 opened this issue Apr 25, 2018 · 7 comments

Comments

@MarkEdmondson1234
Copy link

@MarkEdmondson1234 MarkEdmondson1234 commented Apr 25, 2018

Issue Description

Running the line in the tutorial here:

kubectl patch deploy --namespace kube-system tiller-deploy -p '{"spec":{"template":{"spec":{"serviceAccount":"tiller"}}}}'      

resulted in this error:

Error from server (NotFound): deployments.extensions "tiller-deploy" not found
@MarkEdmondson1234
Copy link
Author

@MarkEdmondson1234 MarkEdmondson1234 commented Apr 25, 2018

I got through this by following this guide:

Step 2: Bind the Tiller service account to the cluster-admin role

Create a tiller-clusterrolebinding.yaml file with the following contents:

  kind: ClusterRoleBinding
  apiVersion: rbac.authorization.k8s.io/v1beta1
  metadata:
    name: tiller-clusterrolebinding
  subjects:
  - kind: ServiceAccount
    name: tiller
    namespace: kube-system
  roleRef:
    kind: ClusterRole
    name: cluster-admin
    apiGroup: ""

Deploy the ClusterRoleBinding:

kubectl create -f tiller-clusterrolebinding.yaml
@judepereira
Copy link

@judepereira judepereira commented Sep 19, 2018

@MarkEdmondson1234 Thanks, that works well.

@EdByrnee
Copy link

@EdByrnee EdByrnee commented Sep 26, 2018

Did not work :(

@judepereira
Copy link

@judepereira judepereira commented Oct 1, 2018

@EdByrnee I wrote a complete guide for this here: https://judepereira.com/blog/nginx-ingress-helm-k8s-rbac/

Can you try that and let me know if it works?

@ToddKopriva
Copy link
Member

@ToddKopriva ToddKopriva commented Jan 2, 2019

@ameer00 , this issue seems to be with a tutorial that you contributed. Could you have a look?

@ameer00
Copy link
Contributor

@ameer00 ameer00 commented Jan 2, 2019

@MarkEdmondson1234, thanks for bringing this to my attention. You do not need to use the kubectl patch command while installing tiller. If you skip that step, everything else should work fine.
Instead of:

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"}}}}'      
helm init --service-account tiller --upgrade

Please use:

kubectl create serviceaccount --namespace kube-system tiller
kubectl create clusterrolebinding tiller-cluster-rule --clusterrole=cluster-admin --serviceaccount=kube-system:tiller   
helm init --service-account tiller

I have a PR in for this already.
Thx

@ToddKopriva
Copy link
Member

@ToddKopriva ToddKopriva commented Jan 8, 2019

I'm closing this issue, because I think that it's addressed by this PR:
#639

Let us know if there's still a problem.

@ToddKopriva ToddKopriva closed this Jan 8, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
5 participants
You can’t perform that action at this time.