-
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
Refactor LimitRange package #4992
Conversation
@vdemeester @skaegi PTAL |
The following is the coverage report on the affected files.
|
/test pull-tekton-pipeline-go-coverage |
The following is the coverage report on the affected files.
|
/test pull-tekton-pipeline-alpha-integration-tests |
/test pull-tekton-pipeline-build-tests |
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.
Looks good and more cleanly separates the tests.
/assign @lbernick |
/lgtm |
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: skaegi, 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:
Approvers can indicate their approval by writing |
/lgtm |
This commit separates logic for calculating a "virtual" limitrange from all limitranges present in a namespace from logic for setting pod compute resources based on the virtual limitrange, and adds tests. This makes it much easier to add tests for scenarios with multiple limitranges and multiple containers, because each component can be tested separately. No functional changes.
The following is the coverage report on the affected files.
|
/lgtm |
Changes
This commit separates logic for calculating a "virtual" limitrange from all limitranges
present in a namespace from logic for setting pod compute resources based on the virtual limitrange,
and adds tests. This makes it much easier to add tests for scenarios with multiple limitranges
and multiple containers, because each component can be tested separately.
No functional changes.
/kind cleanup
Submitter Checklist
As the author of this PR, please check off the items in this checklist:
functionality, content, code)
(if there are no user facing changes, use release note "NONE")
Release Notes