[FEATURE] Override Strategy Step Resources in Build and BuildRuns

[adambkaplan]

Is there an existing feature request for this?

• I have searched the existing feature requests

Is your feature request related to a problem or use-case? Please describe.

Currently, resources such as CPU, memory and ephemeral filesystem storage can only be defined in the Build Strategy step. Developers may need to request additional memory and CPU for specific builds - ex for larger container images.

Describe the solution that you would like.

Builds and BuildRuns should allow step resources to be defined as part of the .spec.strategy:

spec:
...
  strategy:
    name: buildah
    kind: ClusterBuildStrategy
    stepResources:
      - name: build
        resources:
          requests:
            cpu: 2
            memory: 4Gi
...

Describe alternatives you have considered.

Developers/platform teams would need to copy the build strategy and modify the step resources on the fly.

Cluster admins can also utilize LimitRages.

Coming soon to Kubernetes is setting resources at the pod level. This is an alpha feature added to k8s 1.32:

Anything else?

No response

[R3hankhan123]

/assign

[adambkaplan]

Update - Kubernetes pod resource levels have graduated to beta in v1.34 and enabled by default! https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/#pod-level-resource-specification

[adambkaplan]

Tekton also has task-level compute resources as a beta feature: https://tekton.dev/docs/pipelines/compute-resources/#task-level-compute-resources-configuration