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

Kubeflow version vs Jupyter Hub Image Versions Confusion #948

Closed
ultrons opened this issue Mar 9, 2019 · 2 comments
Closed

Kubeflow version vs Jupyter Hub Image Versions Confusion #948

ultrons opened this issue Mar 9, 2019 · 2 comments
Assignees

Comments

@ultrons
Copy link

ultrons commented Mar 9, 2019

We specify a kubeflow version during our One Click Deployment. I chose 0.4.1.
Once we go the pipeline UI and try to start a jupyter hub I am presented with a list of images I can select from based on tensorflow version, cpu/gpu and kubeflow version, and there is no image listed with 0.4.1

It's good to give the user flexibility to select an image with different kubflow version but it's a little confusing as well and at the same time there is no image with the same version chosen at the time of deployment, very confusing.

By the way, the issue aside, Kubeflow pipelines is awesome :)

@Ark-kun
Copy link
Contributor

Ark-kun commented Mar 25, 2019

a list of images I can select from based on tensorflow version, cpu/gpu and kubeflow version, and there is no image listed with 0.4.1

Interesting. I did not notice the images mentioning KF version in addition to the tensorflow version and flavor.

Nevertheless, there is probably not much KF or KFP-specific in those images, so the version does not really matter. You should probably try using the latest version of the KFP package by running

!pip3 install https://storage.googleapis.com/ml-pipeline/release/0.1.13/kfp.tar.gz --upgrade

in the notebook. See the releases page.

By the way, the issue aside, Kubeflow pipelines is awesome :)

Thank you a lot for the feedback!

@Ark-kun Ark-kun self-assigned this Mar 25, 2019
@vicaire
Copy link
Contributor

vicaire commented Mar 26, 2019

Looks like this can be close. Please reopen if there is any oustanding items.

@vicaire vicaire closed this as completed Mar 26, 2019
Linchin pushed a commit to Linchin/pipelines that referenced this issue Apr 11, 2023
HumairAK pushed a commit to red-hat-data-services/data-science-pipelines that referenced this issue Mar 11, 2024
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

3 participants