Create a repository for examples: kubeflow/examples

[jlewi]

I think we should create a repository where we can start hosting E2E examples.

Right now we have a couple E2E examples in various states of development

• https://github.com/cwbeitel/kubeflow-rl - Using TensorFlow Agents for RL
• E2E Solution for GitHub Issue Summarization On Kubeflow #157 GitHub Issue Summarization
• [WIP] Zillow xgb #163 XGB example
• Hot Dog Or Not - Kubeflow Kubecon 2017 demo

/cc @puneith @cwbeitel

[puneith]

@jlewi Why do you think we need a separate repo and not Kubeflow be that place?

[cwbeitel]

I have some additional examples in progress to add.

Would love to have them under e2e test. But for some examples you may want to do progressive testing to speed things up / cache previous runs. Such as with Bazel. That could be a mod to the way kubeflow runs tests or could be a reason to have a separate repo.

[jlewi]

@puneith Because examples will be in various states of development and should probably be separate from the core code.

For the most part, this repo corresponds to our ksonnet registry.

[jlewi]

Another reason for moving examples into their own repository is that it will probably be a different group of folks working on the examples then the folks working on our core ksonnet components.

[puneith]

I agree with that model.

[gaocegege]

Vote for separate repo 👍

[elsonrodriguez]

I could go either way, but my doc fixes have included ksonnet changes. Managing two separate repos for things that are tied together may be painful.

[jlewi]

@elsonrodriguez I think the fact that writing examples requires modifying our core ksonnet components is an indication of other problems

• immaturity/limitations of the ksonnet templates
  • e.g. I think in some of your changes you had to add parameters to the TF serving component to allow more flexibility
• version compatibility issues because we haven't started creating tagged releases yet
  • By March we should have a 0.1 branch for ksonnet registry and our examples should be written against that.

[jlewi]

Lets give a separate repo a shot and then adapt as need be.

I think the main priority now is getting more examples that illustrate Kubeflow so velocity is the primary motivation. With a separate repo we can easily start giving a different set of folks write access and moving the ball forward.

@elsonrodriguez If you want to take the lead on an inception example I'm happy to make you an approver.

[jlewi]

Created the repo:
https://github.com/kubeflow/examples

Created a team examples-approvers and gave it write access to the repo.
I seeded the team with some devrel folks from Google and Microsoft(@wbuchwalter) who've contributed to Kubeflow.

[elsonrodriguez]

@jlewi Sure, I can take the current inception example and rework/port it over.