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.

Sign up for GitHub

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

Jump to bottom

Discussion: Eventing model/solution #263

Closed
aronchick opened this issue Feb 18, 2018 · 2 comments
Closed

Discussion: Eventing model/solution #263

aronchick opened this issue Feb 18, 2018 · 2 comments
Labels
priority/p2

Comments

@aronchick
Copy link
Contributor

Given that training can take a really long time, we should figure out how to fire events at different stages that can be consumed by other tools. Ideally, we'd have a package that ran for on-prem deployments, and then could also use cloud event providers.
@jlewi
Copy link
Contributor

jlewi commented Mar 26, 2018

The TFJob controller has been modified to emit K8s events corresponding to different events (job started/finished) etc...

Do we need more than that?

@jlewi
Copy link
Contributor

jlewi commented Jun 11, 2018

Closing this issue because eventing is being discussed in the context of Argo and Pipelines. We can open up more specific issues as needed to figure out how to integrate various components with them.

@jlewi jlewi closed this as completed Jun 11, 2018
yanniszark pushed a commit to arrikto/kubeflow that referenced this issue Nov 1, 2019
@kunmingg @k8s-ci-robot
update centraldashboard image (kubeflow#263)
6e513b2
elenzio9 pushed a commit to arrikto/kubeflow that referenced this issue Oct 31, 2022
@jinchihe
Apply release team member (kubeflow#263)
272f066
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
priority/p2
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@aronchick @jlewi