You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Would it be possible to track the status of a job in the toplevel DaskJob CR? This would have the advantage of hiding the "implementation details" of the job from a user. I.e. instead of having to know about the state of a job-runner pod that gets created as part of a DaskJob, one could only look at the DaskJob resource to get that information.
A particular use case here would be the Flyte plugin I am currently working on. Most Flyte (backend) plugins work by creating a k8s resource which they continuously poll for updates. The way the plugin machinery is implemented does not allow to reach out to arbitrary k8s resources as the initially created resource is updated and passed into the plugin from the outside.
The exact interface definition is here, where the resource argument in Plugin.GetTaskPhase() would correspond to the DaskJob CR created in Plugin.BuildResource()
Similar Job objects do also set a Status field on their Custom Resources, e.g.:
Would it be possible to track the status of a job in the toplevel
DaskJob
CR? This would have the advantage of hiding the "implementation details" of the job from a user. I.e. instead of having to know about the state of ajob-runner
pod that gets created as part of aDaskJob
, one could only look at theDaskJob
resource to get that information.A particular use case here would be the Flyte plugin I am currently working on. Most Flyte (backend) plugins work by creating a k8s resource which they continuously poll for updates. The way the plugin machinery is implemented does not allow to reach out to arbitrary k8s resources as the initially created resource is updated and passed into the plugin from the outside.
The exact interface definition is here, where the
resource
argument inPlugin.GetTaskPhase()
would correspond to theDaskJob
CR created inPlugin.BuildResource()
Similar Job objects do also set a
Status
field on their Custom Resources, e.g.:ray
: here and herespark
: here and hereHappy to contribute something in case we can align on a format of the status. My initial proposal would be:
This comment has a more detailed explanation on why the current state is blocking the Flyte plugin development.
cc @hamersaw
The text was updated successfully, but these errors were encountered: