-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[TEP-0104] Update Pod with Task-level Resource Requirements #5082
[TEP-0104] Update Pod with Task-level Resource Requirements #5082
Conversation
/hold till #5054 got merged |
The following is the coverage report on the affected files.
|
/release-note-none |
/retest |
7877302
to
68ebb96
Compare
The following is the coverage report on the affected files.
|
/retest |
68ebb96
to
7dd3c71
Compare
The following is the coverage report on the affected files.
|
7dd3c71
to
00e276f
Compare
The following is the coverage report on the affected files.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I know this needs to be rebased onto #5054, but could you keep the scope of this PR to just the changes required to apply the computeResources of a taskrun to a pod? i.e. validation and passing spec from pipelinerun -> taskrun should be covered in #5054.
Also, I think a better place for some of this logic might be pkg/internal/computeresources.
yap. let me keep validation related in #5054. |
00e276f
to
9f19d23
Compare
The following is the coverage report on the affected files.
|
9f19d23
to
0204f00
Compare
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
dee7e64
to
7549113
Compare
The following is the coverage report on the affected files.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks great!
A few notes:
- once Fix Existing Requests and Limits with LimitRange #5269 is merged I think we should add some unit tests to pod_test.go that use the limitrange transformer
- We will need to wait until [TEP-0104]: Update case with limits but no requests community#776 is merged as well
- Please update the docs to clarify the case where a user sets limits but no requests
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: lbernick 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:
Approvers can indicate their approval by writing |
7549113
to
1f77488
Compare
The following is the coverage report on the affected files.
|
/retest |
1f77488
to
a49767e
Compare
The following is the coverage report on the affected files.
|
/retest |
/unhold |
a49767e
to
1740dca
Compare
The following is the coverage report on the affected files.
|
1740dca
to
c5c4005
Compare
The following is the coverage report on the affected files.
|
The task-level compute resource requirements will be applied on the containers created by the Pod.
c5c4005
to
8308f10
Compare
The following is the coverage report on the affected files.
|
/retest |
/lgtm |
Changes
/kind feature
Closes #4470
The related TEP:
TEP-0104: Task-level Resource Requirements
The related impl PRs:
#4877 - Fields Addition & Validation w/ Docs Updates
#5054 - Add Validation for Step-level Resource Requirements
#5212 - Populate Task-level Resource Requirements from PipelineRun to TaskRun
This PR will include logic and tests as:
Submitter Checklist
As the author of this PR, please check off the items in this checklist:
functionality, content, code)
Release Notes