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
The main reason we are considering Kubeflow is the UI which has a user-friendly way of providing run parameters. With the arrival of WorkflowTemplates in v2.5 it seems that Argo is close to a similar user-experience and I think it might be worthwhile to have a similar feature in 'plain' Argo Workflow.
Motivation
We use Argo Workflow for simulations and machine learning. Experimenting with different parameters is important part of the user-experience as they want to test different scenario's. The workflow structure itself hardly changes, but the parameters do. Also the users are data-scientists which can deal with inserting YAML, but would prefer neat fields.
Proposal
In addition to the 'insert-yaml-here' way of submitting a workflow or definitions, provide a user-friendly way to provide parameters. Something like Kubeflow is offering:
ArgoCD already provides such an interface, which takes the defaults from a YAML file. A similar approach can be used:
ArgoCD even shows an emergency icon if the default value has been changed, for clarity:
And is has the option to remove such an override easily. That might be convenient in Argo Workflow when a workflow is replayed:
Message from the maintainers:
If you wish to see this enhancement implemented please add a 👍 reaction to this issue! We often sort issues this way to know what to prioritize.
The text was updated successfully, but these errors were encountered:
Summary
The main reason we are considering Kubeflow is the UI which has a user-friendly way of providing run parameters. With the arrival of WorkflowTemplates in v2.5 it seems that Argo is close to a similar user-experience and I think it might be worthwhile to have a similar feature in 'plain' Argo Workflow.
Motivation
We use Argo Workflow for simulations and machine learning. Experimenting with different parameters is important part of the user-experience as they want to test different scenario's. The workflow structure itself hardly changes, but the parameters do. Also the users are data-scientists which can deal with inserting YAML, but would prefer neat fields.
Proposal
In addition to the 'insert-yaml-here' way of submitting a workflow or definitions, provide a user-friendly way to provide parameters. Something like Kubeflow is offering:
ArgoCD already provides such an interface, which takes the defaults from a YAML file. A similar approach can be used:
ArgoCD even shows an emergency icon if the default value has been changed, for clarity:
And is has the option to remove such an override easily. That might be convenient in Argo Workflow when a workflow is replayed:
Message from the maintainers:
If you wish to see this enhancement implemented please add a 👍 reaction to this issue! We often sort issues this way to know what to prioritize.
The text was updated successfully, but these errors were encountered: