cluster tasks do not define resource limits

[henrjk]

At this time Tekton limits our ability to introduce parameterized resource requests and limits (see PR #196)

For us sometimes typescript builds are failing because of memory issues.

Until there is a good mechanism there should probably be sensible limits defined. In addition this issue can also describe or provide a workaround for those affected.

[henrjk]

As a workaround is to go to the OpenShift web console. Open the Administration View for your projects cd namespace:

• Select Pipelines>Tasks on the left which should open the Tasks view.
• On the Tasks view open tab ClusterTasks and open the task for which you would like to change the resource limits. Copy the YAML to your Clipboard.
• Go back to the Tasks view and select Create/Task with the action button (top right).
• Paste the YAML from the Clipboard and clean up status info, give it a good name and make sure to change the kind to Task. Add a resources section as needed. Then Press Create.
• In your ods.yaml you will have to change the taskRef to adjust for the name change and set kind: Task where is was kind: ClusterTask.

No you can run the task with the new resource limits.

[michaelsauter]

@henrjk Thanks for opening the issue and providing the workaround. This workaround is also described in general nature in https://github.com/opendevstack/ods-pipeline/blob/master/docs/authoring-tasks.adoc#customizing-how-go-applications-are-built. Maybe we can add this use case there as well?

Maybe to provide some more background on this:

The feature has been requested multiple times in the Tekton project, and there are currently two TEPs concerning this issue:

• [Design Proposal] TEP-0094: Specifying Resource Requirements at Runtime tektoncd/community#560
• [TEP-0094]: Rescope to Task resource UX tektoncd/community#588

[gerardcl]

this could be added in the FAQ? shall we create a label to track FAQ additions within GH issues/PRs?

[michaelsauter]

Closing as this is solved to some degree in #404. As tasks are namespaced, the Helm templates defining them can now be used to modify the resources.