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

[cetic/microservice] Isn't bad practice to set resource limits? #2

Open
Nico-Salamone opened this issue Jul 8, 2022 · 0 comments
Open

Comments

@Nico-Salamone
Copy link
Member

Currently, in values.yaml file, resource limits are set. Isn't this a bad practice in Kubernetes?

Is your feature request related to a problem? Please describe.
By default, pods can only use 2 CPUs and 2 GB of memory. If a user of this chart doesn't notice this, they might wonder why a particular pod is "slow".

Describe the solution you'd like
In the values.yaml file, replace this:

resources:
  limits:
    cpu: 2
    memory: 2000Mi
  requests:
    cpu: 500m
    memory: 500Mi

by this:

resources:
  requests:
    cpu: 500m
    memory: 500Mi
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

No branches or pull requests

1 participant