Skip to content

Deployment of driver fails on GKE: assumes that the creator is cluster-admin #66

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

Closed
saad-ali opened this issue Jul 16, 2018 · 1 comment

Comments

@saad-ali
Copy link
Contributor

From Leonid:

So, apparently, deploy_driver.sh example under  gcp-compute-persistent-disk-csi-driver assumes that the creator is cluster-admin, which doesn't looks to be the case for GKE-gcloud-connect.
Manually creating relevant binding:
kubectl create clusterrolebinding cluster-admin-binding   --clusterrole cluster-admin   --user $(gcloud config get-value account)

seems to be enough to make the deployment work.

I verified his recommendation got me past this issue.

@msau42
Copy link
Contributor

msau42 commented Jul 16, 2018

Ah I think this is the issue that in order to create a clusterrole, you need to be cluster admin, and gke doesn't map the Kubernetes admin role to your IAM account by default.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants