Bump kelos-workers and kelos-pr-responder task memory to 1Gi#1163
Open
gjkim42 wants to merge 1 commit into
Open
Bump kelos-workers and kelos-pr-responder task memory to 1Gi#1163gjkim42 wants to merge 1 commit into
gjkim42 wants to merge 1 commit into
Conversation
Recent kelos-workers tasks were evicted under node memory pressure because the claude-code container regularly uses ~1.2-1.3 GiB while only requesting 512 MiB. Bumping the request to 1 GiB reduces the QoS-eviction risk for the two spawners that run the heaviest claude-code workloads.
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
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.
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
Bumps the
claude-codecontainer memory request from512Mito1Gifor thekelos-workersandkelos-pr-responderTaskSpawners.Multiple recent
kelos-workers-issue-comment-*tasks failed with pod evictions on the node. Inspecting the evicted pods showed claude-code routinely using ~1.2–1.3 GiB of memory while only requesting 512 MiB:Because the pods are
BurstableQoS, they're first in line for kubelet eviction under node memory pressure. Bumping the request to 1 GiB brings it closer to actual usage and reduces the eviction risk. Scope is limited to the two spawners running the heaviest claude-code workloads — the other spawners can be revisited if they start showing the same failure mode.Which issue(s) this PR is related to:
N/A
Special notes for your reviewer:
Only
requests.memoryis bumped; no limit is set on memory (existing behavior preserved).ephemeral-storageandcpuare unchanged.Does this PR introduce a user-facing change?
Summary by cubic
Increase
claude-codememory request from 512Mi to 1Gi forkelos-workersandkelos-pr-responderto prevent pod evictions under memory pressure. Onlyrequests.memorychanged; CPU andephemeral-storageare unchanged, and there is still no memory limit.Written for commit 9ae35ec. Summary will update on new commits. Review in cubic