Add CPU resource request to elasticsearch pod#385
Open
asafyehezkel wants to merge 2 commits into
Open
Conversation
Elasticsearch declared a memory request/limit but no CPU request, so the scheduler had no guaranteed CPU floor for the ES pod. Add a 1-core CPU request (no limit, to avoid throttling a latency-sensitive workload). Fixes EN-2222.
A full-core request makes ES claim ~50% of a 2-vCPU node (small VMs, Docker Desktop defaults), risking Pending pods since the k3d installer never validates CPU capacity. 500m keeps the scheduling floor while staying schedulable on minimum hardware; no CPU limit, so it still bursts freely. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
The Elasticsearch pod declared a memory request/limit but no CPU request, so the scheduler had no guaranteed CPU floor for it. Add a 1-core CPU request under
resources.requests.No CPU limit is set, to avoid throttling a latency-sensitive workload. Verified the chart still renders with
helm template.Fixes EN-2222.