Update samples page to show which version of Kubelow each sample works with

[jlewi]

This page https://www.kubeflow.org/docs/examples/kubeflow-samples/

lists a lot of samples that I don't think are updated for 0.7.

• Should we remove samples until they have been updated for 0.7?

• Should we add the xgboost_synthetic ?

  • That is probably the sample most up to date for 0.7

• code_search is pretty stale at this point as are some other samples so we should probably remove that one.

• I think @amygdala might have made some updates to github issue summarization recently

[issue-label-bot[bot]]

Issue-Label Bot is automatically applying the label kind/feature to this issue, with a confidence of 0.54. Please mark this comment with :thumbsup: or :thumbsdown: to give our bot feedback!

Links: app homepage, dashboard and code for this bot.

[jlewi]

@sarahmaddox suggested not removing the list of samples but instead with each one listing the Kubeflow versions they work with.

[sarahmaddox]

/good-first-issue

[k8s-ci-robot]

@sarahmaddox: This request has been marked as suitable for new contributors.

Please ensure the request meets the requirements listed here.

If this request no longer meets these requirements, the label can be removed by commenting with the /remove-good-first-issue command.

In response to [this](https://github.com/kubeflow/website/issues/1316): >/good-first-issue Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.

[janeman98]

@sarahmaddox Is there an easy way to find out what version these sample work with?

I have a quick look on these samples, most of them just point to "Getting Started with Kubeflow" Semantic code search -- > Getting Started with Kubeflow (https://www.kubeflow.org/docs/started/getting-started/) Financial time series --> KUBEFLOW_VERSION=0.2.5 ?? GitHub issue summarization --> v0.4.0-rc.2. MNIST image classification -- > Getting Started with Kubeflow Object detection - cats and dogs -- > Getting Started with Kubeflow PyTorch MNIST --> Getting Started with Kubeflow Ames housing value prediction --> Getting Started with Kubeflow

[sarahmaddox]

@texasmichelle and @amygdala Can you help identify the Kubeflow version for each sample?

[amygdala]

I should have some time to tackle it week after next. (Most aren't "mine" and I don't know their current status). The github summarization/pipelines one is mine, and has been updated to work with 0.7. (Note: that's the pipelines subdir of that example.)

[hefedev]

I'd like to jump on this one if possible. To figure out which version works, I'll look at the CONFIG_FILE url and which master branch it points towards. This always worked for me before.

[sarahmaddox]

/assign @hefedev

Thanks @hefedev!

[sarahmaddox]

@hefedev I've moved this issue to In progress in the doc sprint Kanban board, because the issue is assigned to you. Happy sprinting!

[hefedev]

Thank you @sarahmaddox for the opportunity, I submitted my first changes for feedback. I'll get back on this asap.

[amygdala]

I'm not sure this should be closed yet? I believe we're still testing many of these examples with the KF 1 RC. @jlewi @sarahmaddox cc @velascoluis, who is helping with this.

[sarahmaddox]

Thanks @amygdala that's excellent news. Let's keep this issue as closed, because it originally related to v0.7 and because @hefedev has implemented a solution using Hugo block parameters and the GitHub API.

How about raising another issue for v1.0. If we need to manually override the results from the API, we can do that via the parameters that feed into the block.

[amygdala]

Just a note so it doesn't get lost: https://github.com/kubeflow/examples/blob/master/pipelines/mnist-pipelines/mnist_pipeline.py turns out to be broken (in 0.7 too, I believe, given the nature of the probs).

I think Jeremy did create such an issue for 1.0 already; let me confirm.