fix: raise manager memory limit to 2Gi (OOMKilled crash-loop)#138
Merged
Conversation
The manager OOMKilled-crash-looped on a fresh pod: 512Mi can't hold the cold-start informer cache spike (cluster-wide Secret/ConfigMap/Namespace caches) on large clusters. The previous pod only survived because its cache was warmed long ago. Raise limit 512Mi->2Gi, request 128Mi->512Mi. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #138 +/- ##
==========================================
+ Coverage 48.22% 49.16% +0.93%
==========================================
Files 8 8
Lines 960 960
==========================================
+ Hits 463 472 +9
+ Misses 433 427 -6
+ Partials 64 61 -3 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
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
1 participant
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.
Problem
A fresh manager pod OOMKilled crash-loops (43 restarts observed):
512Mican't hold the cold-start informer cache spike — the controllers watch Secrets/ConfigMaps/Namespaces cluster-wide, and on a large (225-node) cluster the initial LIST exceeds the limit. The long-running pod only survived because its cache was warmed when the cluster was smaller; any restart now crash-loops.Manager
lastState.terminated:reason=OOMKilled exitCode=137, crash begins right after cache/leader-election startup, before any reconcile.Fix
Raise the manager limit
512Mi → 2Giand request128Mi → 512Mi. Config-only; synced by thespcld-argocd-complementary-operatorArgo app.(Follow-up worth considering separately: scope the Secret/ConfigMap watches with field/namespace selectors to cut steady-state memory.)
🤖 Generated with Claude Code