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

[GH Example] Friction points from Katacoda #88

Closed
1 task
texasmichelle opened this issue Apr 20, 2018 · 2 comments
Closed
1 task

[GH Example] Friction points from Katacoda #88

texasmichelle opened this issue Apr 20, 2018 · 2 comments

Comments

@texasmichelle
Copy link
Member

Katacoda recently created a scenario out of the GitHub issue summarization example and ran into a number of frustrating issues. The following items need to be addressed in order to turn this example into a platform-independent self-contained unit for use in a wide number of environments.

@jlewi
Copy link
Contributor

jlewi commented Apr 20, 2018

Could we follow an approach similar to using a bootstrap container as being discussed in kubeflow/kubeflow#673

The idea is users would do something like
kubectl create -f http://github.com/kubeflow/examples/ghissue-bootstrap.yaml
kubectl exec -it gh-bootstrap /bin/bash
quickstart.sh

The goal is that quickstart.sh would set everything up and try to optimize things for their config. This gives them a shell they can drop into with all the tools/code they need.

Could Katacoda reuse these container images?

@jlewi
Copy link
Contributor

jlewi commented Apr 27, 2018

Duplicate of #89

@jlewi jlewi marked this as a duplicate of #89 Apr 27, 2018
@jlewi jlewi closed this as completed Apr 27, 2018
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

2 participants