Set Elasticsearch Pod default memory limit to 2Gi #1810
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Similar to how we set a default request of 2Gi to prevent the Pod from
being scheduled on a node without at least 2Gi memory, let's set a
default memory request of 2Gi. Which should prevent the Pod from being
the first one evicted on a node running out of memory.
Those defaults can be overridden by the user, or disabled entirely by
providing an empty (
{}
) memory requests or limits.If either limits or requests is provided by the user (or both), we don't
apply our default resources requirements.
No default CPU is set.
Fixes the ES part of #1454.