fix(image-updater): give the controller room for its start-up warm-up - #574
Merged
Merged
Conversation
chomatdam
force-pushed
the
fix/image-updater-memory
branch
from
September 27, 2026 21:20
b2bcbc1 to
ba1d400
Compare
5.1.3 moved the chart to 1.3.1, whose controller lists every Application when it starts. The 105M limit, from a 2022 note for the old single-process updater, OOMKills that warm-up on a cluster with a few hundred Applications while the process idles well under it once through.
chomatdam
force-pushed
the
fix/image-updater-memory
branch
from
September 27, 2026 21:20
ba1d400 to
e8fad6b
Compare
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.
What
5.1.3 merged #559, moving argocd-image-updater to chart 1.3.1. The v1.3 controller lists every Application at start-up, and the component's 105M memory limit, from a 2022 upstream note for the old single-process updater, OOMKills that warm-up on a cluster with a few hundred Applications (exit 137 about 16 s after start). Once through, the process idles well under the old limit, so the failure is start-up headroom only, and every restart replays it.
Change
memory limit and request 105M → 256Mi (request kept equal to the limit), cpu request unchanged.
🤖 Generated with Claude Code