8000 Remove default resources requests and limits - they should be set exp… by evilr00t · Pull Request #4448 · kserve/kserve · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Remove default resources requests and limits - they should be set exp… #4448

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

evilr00t
Copy link
@evilr00t evilr00t commented May 6, 2025

…licitly by the operator

What this PR does / why we need it:

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

Type of changes
Please delete options that are not relevant.

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update

Feature/Issue validation/testing:

This change removes default limits and requests that can't be overwritten by operator if we want for example remove CPU limit or remove Memory limit, those limits will be inherited from default values.yaml. Operator should set its own limits when needed. If default values are required - please let me know I can update template files.

Please describe the tests that you ran to verify your changes and relevant result summary. Provide instructions so it can be reproduced.
Please also list any relevant details for your test configuration.

  • helm template .

  • Logs

Special notes for your reviewer:

  1. Please confirm that if this PR changes any image versions, then that's the sole change this PR makes.

Checklist:

  • Have you added unit/e2e tests that prove your fix is effective or that this feature works?
  • Has code been commented, particularly in hard-to-understand areas?
  • Have you made corresponding changes to the documentation?

Release note:


Re-running failed tests

  • /rerun-all - rerun all failed workflows.
  • /rerun-workflow <workflow name> - rerun a specific failed workflow. Only one workflow name can be specified. Multiple /rerun-workflow commands are allowed per comment.

@spolti
Copy link
Contributor
spolti commented May 16, 2025

Can you please help with signing your commit?

@evilr00t evilr00t force-pushed the flexible-limits branch 2 times, most recently from 468525d to b82088d Compare May 19, 2025 09:14
@evilr00t
Copy link
Author

Can you please help with signing your commit?

that's done now. Thank you for letting me know.

@evilr00t evilr00t force-pushed the flexible-limits branch 2 times, most recently from a72abc8 to 8539a2f Compare May 22, 2025 09:19
@spolti
Copy link
Contributor
spolti commented May 27, 2025

@sivanantha321 can you please take a look?

…licitly by the operator

Signed-off-by: Karol Czeryna <k@e-dot.uk>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants
0