Skip to content
This repository has been archived by the owner on Dec 12, 2022. It is now read-only.

Umbrella issue for ML Workflows on OpenShift content #11

Closed
willb opened this issue Mar 18, 2020 · 6 comments
Closed

Umbrella issue for ML Workflows on OpenShift content #11

willb opened this issue Mar 18, 2020 · 6 comments
Labels
FDE lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Comments

@willb
Copy link

willb commented Mar 18, 2020

It would be nice to have the content from the [https://github.com/willb/openshift-ml-workflows-workshop](ML workflows workshop) available in Katacoda. Individual scenarios will link back to this issue.

@willb
Copy link
Author

willb commented Mar 18, 2020

(cc @sophwats)

@4n4nd
Copy link

4n4nd commented Mar 18, 2020

@willb maybe you could start with adding a Dockerfile to your repo that builds a jupyter notebook image just like this. Since we are using your template, it should be very similar.

@sesheta
Copy link

sesheta commented Jul 1, 2021

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@sesheta sesheta added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jul 1, 2021
@sesheta
Copy link

sesheta commented Oct 12, 2021

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle rotten

@sesheta sesheta added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Oct 12, 2021
@sesheta
Copy link

sesheta commented Nov 11, 2021

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

@sesheta sesheta closed this as completed Nov 11, 2021
@sesheta
Copy link

sesheta commented Nov 11, 2021

@sesheta: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

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.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
FDE lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
None yet
Development

No branches or pull requests

4 participants