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
Move troubleshooting guide into user_guide #223
Labels
Milestone
Comments
The relevant information is in the troubleshooting guide in our README.md The fact that the information is not in our user_guide seems undesirable. I suggest moving the troubleshooting guide into the user_guide. On the main page we should update the troubleshooting information to just be a link to the relevant section in the user_guide. |
jlewi
changed the title
Issue with user guide for GKE
Move troubleshooting guide into user_guide
Feb 10, 2018
I can take a stab at this. |
Pull request out for review. |
Merged
jlewi
pushed a commit
that referenced
this issue
Feb 12, 2018
* moving the troubleshooting guide into the user_guide. * in README update the troubleshooting information to just be a link to the relevant section in the user_guide. * Fix #223
yanniszark
pushed a commit
to arrikto/kubeflow
that referenced
this issue
Nov 1, 2019
- fix problems affecting installations - update image versions
elenzio9
pushed a commit
to arrikto/kubeflow
that referenced
this issue
Oct 31, 2022
contributing to kfp-tekton work
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Following the instruction for user_guide.md, saw the following error.
I am on google cloud GKE
my-kubeflow ks apply ${KF_ENV} -c kubeflow-core
INFO Updating services kubeflow.k8s-dashboard
INFO Updating services kubeflow.tf-hub-0
INFO Updating services kubeflow.tf-hub-0
INFO Updating clusterrolebindings ambassador
INFO Updating roles kubeflow.jupyter-role
INFO Creating non-existent roles kubeflow.jupyter-role
ERROR Error updating roles kubeflow.jupyter-role: roles.rbac.authorization.k8s.io "jupyter-role" is forbidden: attempt to grant extra privileges: [PolicyRule{Resources:[""], APIGroups:[""], Verbs:[""]}] user=&{blad@blah.com [system:authenticated] map[]} ownerrules=[PolicyRule{Resources:["selfsubjectaccessreviews"], APIGroups:["authorization.k8s.io"], Verbs:["create"]} PolicyRule{NonResourceURLs:["/api" "/api/" "/apis" "/apis/" "/healthz" "/swaggerapi" "/swaggerapi/" "/version"], Verbs:["get"]} PolicyRule{NonResourceURLs:["/swagger-2.0.0.pb-v1"], Verbs:["get"]} PolicyRule{NonResourceURLs:["/swagger.json"], Verbs:["get"]}] ruleResolutionErrors=[]
Saw this change, and followed the following and it worked.
Should we add it back to the doc?
-### Google Kubernetes Engine
-Google Kubernetes Engine is a managed environment for deploying Kubernetes applications powered by Google Cloud.
-If you're using Google Kubernetes Engine, prior to creating the manifests, you must grant your own user the requisite RBAC role to create/edit other RBAC roles.
-
commandline -kubectl create clusterrolebinding default-admin --clusterrole=cluster-admin --user=user@gmail.com -
The text was updated successfully, but these errors were encountered: