Skip to content
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

Defaults CPU requests for reload container too high #1235

Open
datamuc opened this issue Feb 10, 2025 · 0 comments
Open

Defaults CPU requests for reload container too high #1235

datamuc opened this issue Feb 10, 2025 · 0 comments
Labels
enhancement New feature or request good first issue Good for newcomers

Comments

@datamuc
Copy link

datamuc commented Feb 10, 2025

Currently all the configReloaders have default cpu requests like this

# memory omitted here they look ok to me
resources:
  requests:
    cpu: 100m

I think that is too much. If you spin up 5 vmauth half a cpu is gone just for triggering a config reload.

So I propose something like this:

resources:
  requests:
    cpu: 10m
  limits:
    cpu: 50m

Or maybe even 10m/10m (not sure about that). But the above is what I did to my deployments.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

2 participants