-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
[tempo-distributed] Added resource limit and request samples for all components #3452
base: main
Are you sure you want to change the base?
Conversation
d80774e
to
5dabb79
Compare
Hi, |
5dabb79
to
e9d1a89
Compare
Please don't add CPU limit as it is impossible to remove the CPU limit entirely then. |
Hi @Starefossen, If you are referring to the enterprise section, for the sake of consistency, since this was the only section on which resource request was set by default I did not comment out the limits as well. Now I have commented the section (since the default value itself was very low as well). Cheers |
Signed-off-by: xogoodnow <[email protected]>
Signed-off-by: xogoodnow <[email protected]>
Signed-off-by: xogoodnow <[email protected]>
Signed-off-by: xogoodnow <[email protected]>
b729ebe
to
b54655e
Compare
Signed-off-by: xogoodnow <[email protected]>
Yes, the comments are no problem. It was just regarding any default values. Sorry for the confusion. |
Thank you, NP. |
Signed-off-by: xogoodnow <[email protected]>
Signed-off-by: xogoodnow <[email protected]>
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.
Thanks of for the PR. I think the comments are good, but not sure about the default values on the two components which add them.
@@ -1747,6 +1807,9 @@ minio: | |||
persistence: | |||
size: 5Gi | |||
resources: | |||
limits: | |||
cpu: 100m | |||
memory: 128Mi |
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.
I expect this to be too small to be useful, but I don't have an example to check at the moment.
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.
This seems more reasonable
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.
How about commenting out the resource section for Minio as well?!
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.
Yep, I agree. I think folks can place their own limits here. Scale will matter, so choosing sane defaults is a bit difficult.
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.
exactly.
@zalegrala, If there is anything that I should do please let me know. |
Signed-off-by: Ali <[email protected]>
Signed-off-by: xogoodnow <[email protected]>
Signed-off-by: xogoodnow <[email protected]>
I disagree with adding default requests/limits for minio and admin api. The only part of this PR i'm in strong agreement with is removing the requests for enterprise gateway. Even the comments just feel like they're cluttering the file. |
Hi @joe-elliott, IMHO, setting comments for resources is quite convenient and is a very common practice within all mature helm charts. p.s: On most managed K8S platforms, users have to set request and limit for every pod so when using this chart they have to manually copy and paste the section throughout the whole chart (just wanted to clarify what I meant by convince). Cheers |
Added commented sample for request and limit for components
Having the comments is quite convenient.