Open digglife opened 2 years ago
Hi @digglife its a great question. We have another enhancement that talks about advanced configuration for tasks where you could specify time outs or no network access or secrets and more.
But w.r.t. timeout would be a great addition but does pose security concerns in that you wouldn't want a user to set a task with 24hour timeouts as that could mess up the cluster if too many were run with that sort of timeout.
What would probably need to happen is a quota introduced for timeout, with a default specified timeout. And then a user could adjust within the quota. OR maybe the workflow timeout overall will kill any tasks that exceed the whole workflow timeout.
@BenjaminRuby to check with @gchickma on the importance for IBM in this.
For now bumping this from 3.8.0
This is available in v4 both at a WorkflowRun and TaskRun level.
Needs to be added to the UI to make available. Tagged for Flow 4.0.0
@timrbula we need to add the timeout and retries fields to the Workflow / Tasks. Considering right now in the UI its hard to edit each task's configuration... for now we should add to the Workflows config screen
Future state might be to add a tab to the Tasks modal or move that to a right hand panel
This has been implemented for the Workflow and is linked to Quotas.
Need to implement specific settings per task somehow
Implemented via the API
Could be implemented a couple of different ways in the UI
Is your request related to a problem? Please describe.
There is a setting for Flow administrator to change the Timeout of TaskRun, which is now by default 180 minutes. If user's flow needs longer than 180 minutes to complete, he has to ask Administrator to change it.
Describe the solution you'd like
Allow users to customize the Timeout of TaskRun.
Describe the benefits or justification for this request
Users can help themselves adjust the timeout, without asking the administrator.