-
Notifications
You must be signed in to change notification settings - Fork 835
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
feat(defaults): Add default resources to engine/executor container #2514
Conversation
Hi @groszewn. Thanks for your PR. I'm waiting for a SeldonIO member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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 jenkins-x/lighthouse repository. |
@groszewn I'm just wondering if we should be more conservative on the CPU as a value of 1 implies continuous usage in a cluster. Given we are not serverless I am wondering if this could cause issues to existing users that have over-commits for their cluster? |
@cliveseldon I think that's a very valid concern. Would it make sense for this value to be configurable via the helm chart install so that cluster admins can specify what meets their needs best and have a lower default (maybe 0.5 or lower)? |
@groszewn Yes I think that makes sense
|
acd341d
to
d5ff6c7
Compare
d5ff6c7
to
98c4d11
Compare
@cliveseldon updated to make the default resources configurable via the helm chart install. |
/ok-to-test |
Mon Oct 5 12:49:33 UTC 2020 impatient try |
Mon Oct 5 12:49:35 UTC 2020 impatient try |
@cliveseldon do the test need to be rekicked? |
/test integration |
Tue Oct 6 13:09:43 UTC 2020 impatient try |
/retest |
Wed Oct 7 12:34:13 UTC 2020 impatient try |
@groszewn: The following test failed, say
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 jenkins-x/lighthouse repository. I understand the commands that are listed here. |
98c4d11
to
3e6fe28
Compare
Fri Oct 9 13:06:16 UTC 2020 impatient try |
Fri Oct 9 13:06:50 UTC 2020 impatient try |
@cliveseldon seems like the |
/retest |
/test lint |
Tue Oct 13 16:53:56 UTC 2020 impatient try |
@axsaucedo looks like PR checks have passed, do you need to kick the longer-running tests (I'm not sure if I have this capability and don't want to overstep and strain the build system). |
Defines default requests and limits on the engine/executor container. Contributes to 2475 Signed-off-by: Nick Groszewski <groszewn@gmail.com>
3e6fe28
to
089181a
Compare
Thu Oct 15 14:26:10 UTC 2020 impatient try |
Thu Oct 15 14:26:19 UTC 2020 impatient try |
/approve |
Thank you @groszewn ! |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: axsaucedo 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 |
Defines default requests and limits on the engine/executor container.
Contributes to #2475
Signed-off-by: Nick Groszewski groszewn@gmail.com
What this PR does / why we need it:
Addition of default engine/executor container resources, which helps in clusters with OPA policies defined to require requests and limits be set.
Which issue(s) this PR fixes:
Fixes #2475
Special notes for your reviewer:
Does this PR introduce a user-facing change?: