apply default-container-resource-requirements before LimitRange transformer

[jkandasa]

Changes

The PR changing the order of execution, default-container-resource-requirements will be applied before LimtRange transformer. To make the code easy maintainability, I have created a new transformer for default-container-resource-requirements and moved the existing code to there.

transformer added as follows,

pod, err := podbuilder.Build(ctx, tr, *ts,
	defaultresourcerequirements.NewTransformer(ctx), // default-container-resource-requirements
	computeresources.NewTransformer(ctx, tr.Namespace, c.limitrangeLister), // limitRange transformer
	affinityassistant.NewTransformer(ctx, tr.Annotations),
)

• fixes: default resource requirements should be executed before LimitRange transformer #8196
• default-container-resource-requirements was originally added on add default resource requirements to init-containers and containers of a pod #7003

/kind bug

Submitter Checklist

As the author of this PR, please check off the items in this checklist:

• Has Docs if any changes are user facing, including updates to minimum requirements e.g. Kubernetes version bumps
• Has Tests included if any functionality added or changed
• pre-commit Passed
• Follows the commit message standard
• Meets the Tekton contributor standards (including functionality, content, code)
• Has a kind label. You can add one by adding a comment on this PR that contains /kind <type>. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tep
• Release notes block below has been updated with any user facing changes (API changes, bug fixes, changes requiring upgrade notices or deprecation warnings). See some examples of good release notes.
• Release notes contains the string "action required" if the change requires additional action from users switching to the new release

Release Notes

[Bug fix]: `default-container-resource-requirements` will be applied to the container before `LimtRange`

[tekton-robot]

The following is the coverage report on the affected files.
Say /test pull-tekton-pipeline-go-coverage to re-run this coverage report

File	Old Coverage	New Coverage	Delta
pkg/internal/defaultresourcerequirements/transformer.go	Do not exist	100.0%
pkg/pod/pod.go	93.9%	92.9%	-1.1

[tekton-robot]

The following is the coverage report on the affected files.
Say /test pull-tekton-pipeline-go-coverage-df to re-run this coverage report

File	Old Coverage	New Coverage	Delta
pkg/internal/defaultresourcerequirements/transformer.go	Do not exist	100.0%
pkg/pod/pod.go	93.9%	92.9%	-1.1

[jkandasa]

/cc @vdemeester

[vdemeester]

/cc @chitrangpatel

[tekton-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: vdemeester

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [vdemeester]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[chitrangpatel]

/lgtm

[jkandasa]

/cherry-pick release-v0.62.x

[tekton-robot]

@jkandasa: new pull request created: #8227

In response to this:

/cherry-pick release-v0.62.x

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[jkandasa]

/cherry-pick release-v0.59.x

[tekton-robot]

@jkandasa: #8197 failed to apply on top of branch "release-v0.59.x":

Applying: apply default-container-resource-requirements before LimitRange transformer
Using index info to reconstruct a base tree...
M	pkg/pod/pod.go
M	pkg/pod/pod_test.go
M	pkg/reconciler/taskrun/taskrun.go
Falling back to patching base and 3-way merge...
Auto-merging pkg/reconciler/taskrun/taskrun.go
Auto-merging pkg/pod/pod_test.go
CONFLICT (content): Merge conflict in pkg/pod/pod_test.go
Auto-merging pkg/pod/pod.go
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 apply default-container-resource-requirements before LimitRange transformer
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to this:

/cherry-pick release-v0.59.x

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.