-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
"getting-started-gke" installer fails #1201
Comments
it seem like kubectl 1.11.0 is buggy and responsible for the failed deployment. |
/assign me |
@ankushagarwal: GitHub didn't allow me to assign the following users: me. Note that only kubeflow members and repo collaborators can be assigned. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/assign ankushagarwal |
@mmatiaschek : Do you know what the problem with ksonnet was? I've not had issues with 1.11.0 Regarding the
|
@mmatiaschek The tmp issue should be fixed in 0.2.2-rc.0 |
0.2.2-rc.0 has been promoted to 0.2.2. |
* 0.2.2 includes some fixes to deploy.sh. Fix kubeflow/kubeflow#1201
* Bump the Kubeflow version from 0.2.1 to 0.2.2. * 0.2.2 includes some fixes to deploy.sh. Fix kubeflow/kubeflow#1201 * Update the user_guide. * Fix the user_guide.md
Thank you, it works... i still have some problems though, i will open another issue |
I had these issues on google cloud shell so i tried with a fresh install on Bash on Ubuntu on Windows, Ubuntu 16.04, and got the same problems.
First issue with the kubeflow documentation/installer was that the tmp folder was not found, my workaround was to
mv /tmp/kubeflow-0.2.1/ /tmp/kubeflow-v0.2.1
and start again.The next error was not recoverable for me, any help would be greatly appreciated!!
The text was updated successfully, but these errors were encountered: