-
Notifications
You must be signed in to change notification settings - Fork 364
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
bump resource limits for Envoy Gateway deployment #1617
Conversation
Relates to envoyproxy#1613 Signed-off-by: Arko Dasgupta <[email protected]>
Codecov Report
@@ Coverage Diff @@
## main #1617 +/- ##
==========================================
- Coverage 61.79% 61.70% -0.10%
==========================================
Files 81 81
Lines 12031 12031
==========================================
- Hits 7435 7424 -11
- Misses 4138 4146 +8
- Partials 458 461 +3 |
/retest |
requests: | ||
cpu: 10m | ||
memory: 64Mi | ||
cpu: 100m |
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.
the requests
does not need to increase. EG can run on cpu 10m and mem 64Mi. for the limits IMO can't fix memory hign usage. #1613 (comment)
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 is a a rough estimate on what values would satisfy lower and upper bounds for common case
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 see, but requests changing is unnecessary from my production env situation.
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.
isn't 10m
too low to start off with ?
Relates to #1613
Must be revisited again when #1365 is completed