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
{{ message }}
This repository has been archived by the owner on Aug 9, 2024. It is now read-only.
Currently the benchmarking kubeflow job is configured through config file, while the post processor is configured through ksonnet with limited functionality (only allows image and commands). Letting the post processor be configured same way as kubeflow job makes it more consistent and also helps to make the post processor fully functional. We can allow post job to be specified in any way that conforms to kubernetes job object.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Currently the benchmarking kubeflow job is configured through config file, while the post processor is configured through ksonnet with limited functionality (only allows image and commands). Letting the post processor be configured same way as kubeflow job makes it more consistent and also helps to make the post processor fully functional. We can allow post job to be specified in any way that conforms to kubernetes job object.
The text was updated successfully, but these errors were encountered: