From 9d4bc9e8050df067da8416314e5cc8572a965d76 Mon Sep 17 00:00:00 2001
From: Lee Bernick <lee.a.bernick@gmail.com>
Date: Mon, 8 Nov 2021 11:24:29 -0500
Subject: [PATCH] [Problem Statement] TEP for specifying resource requirements
 at runtime

This TEP addresses tektoncd/pipeline#4080 and tektoncd/pipeline#4326 by
proposing new configuration to TaskRuns and PipelineTaskRuns that can
override any Step resource requirements specified in a Task or PipelineTask.
---
 teps/0094-step-resources-at-runtime.md | 61 ++++++++++++++++++++++++++
 teps/README.md                         |  1 +
 2 files changed, 62 insertions(+)
 create mode 100644 teps/0094-step-resources-at-runtime.md

diff --git a/teps/0094-step-resources-at-runtime.md b/teps/0094-step-resources-at-runtime.md
new file mode 100644
index 000000000..c2f8925b3
--- /dev/null
+++ b/teps/0094-step-resources-at-runtime.md
@@ -0,0 +1,61 @@
+---
+status: proposed
+title: Step Resources at Runtime
+creation-date: '2021-11-08'
+last-updated: '2021-11-08'
+authors:
+- '@lbernick'
+---
+
+# TEP-0094: Step Resources at Runtime
+
+<!-- toc -->
+- [Summary](#summary)
+- [Motivation](#motivation)
+  - [Goals](#goals)
+  - [Non-Goals](#non-goals)
+  - [Use Cases](#use-cases)
+- [Requirements](#requirements)
+<!-- /toc -->
+
+## Summary
+Add runtime configuration options for setting resource requirements of `Step`s.
+
+Currently, users can specify resource requirements in a `Task` definition,
+via the `Resources` field of each `Step`. However, there is currently no support
+for modifying these requirements in a `TaskRun` or `PipelineTaskRun`.
+
+This TEP proposes adding a configuration option to `TaskRun` and `PipelineTaskRun`
+to override any `Step` resource requirements specified in a `Task` or `PipelineTask`.
+
+## Motivation
+Compute resource requirements typically depend on runtime constraints.
+The following issues contain user requests for being able to modify resource requirements at runtime:
+
+- [Allow usage of variable replacement when defining resource limits and requests](https://github.com/tektoncd/pipeline/issues/4080)
+- [Support specifying resource requests at TaskRun level](https://github.com/tektoncd/pipeline/issues/4326)
+
+### Goals
+
+Add configuration to `TaskRun` and `PipelineTaskRun` allowing users to specify resource requirements
+of `Step`s defined in a `Task` or `PipelineTask`.
+
+### Non-Goals
+
+- Ability to override other `Step` fields in a `TaskRun` or `PipelineTaskRun`.
+- Ability to specify combined resource requirements of all `Step`s at `Task` or `Pipeline` level.
+While this may be a valuable feature, it should be considered in a separate proposal.
+
+### Use Cases
+
+- Image or code building `Task`s can use different amounts of compute resources
+depending on the image or source being built.
+- Kubeflow pipelines and other data pipelines may have variable resource requirements
+depending on the data being processed.
+
+## Requirements
+
+- Users can specify `Step` resource requirements at runtime.
+- Users can specify `Step` resource requirements for `Task`s or `Pipeline`s they don't own,
+especially those in the Catalog.
+- Users can specify resource requirements for individual `Step`s.
\ No newline at end of file
diff --git a/teps/README.md b/teps/README.md
index 3b1917838..4103e9c60 100644
--- a/teps/README.md
+++ b/teps/README.md
@@ -227,3 +227,4 @@ This is the complete list of Tekton teps:
 |[TEP-0082](0082-workspace-hinting.md) | Workspace Hinting | proposed | 2021-10-26 |
 |[TEP-0084](0084-endtoend-provenance-collection.md) | end-to-end provenance collection | proposed | 2021-09-16 |
 |[TEP-0085](0085-per-namespace-controller-configuration.md) | Per-Namespace Controller Configuration | proposed | 2021-10-14 |
+|[TEP-0094](0094-step-resources-at-runtime.md) | Step resource requirements at runtime |  proposed | 2021-11-08 |