Open
Conversation
slawande2
requested review from
alcasim,
bennerv,
cadenmarchese,
hawkowl,
hlipsig,
jharrington22,
kevinobriendotca,
kimorris27,
mociarain,
mrWinston,
rogbas,
sankur-codes,
tiguelu,
tsatam,
tuxerrante,
ventifus,
wanghaoran1988 and
yjst2012
as code owners
Contributor
There was a problem hiding this comment.
Pull request overview
This PR increases the Podman container memory limit for the aro-rp systemd service to reduce OOM kills under peak regional installation concurrency, aligning the generated deployment asset with the updated generator script.
Changes:
- Update
aro-rpservice container memory limit from2gto4gin the service definition. - Regenerate/update the production gateway ARM template asset to include the new
aro-rpmemory limit.
Reviewed changes
Copilot reviewed 1 out of 3 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| pkg/deploy/generator/scripts/util-services.sh | Bumps aro-rp container memory limit to 4g in the systemd podman run command generated for gateway hosts. |
| pkg/deploy/assets/gateway-production.json | Updates the embedded CustomScript payload so the deployed aro-rp service uses -m 4g. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
tsatam
approved these changes
Apr 23, 2026
cadenmarchese
approved these changes
Apr 23, 2026
slawande2
force-pushed
the
slawande/bump-rp-memory-4g
branch
from
374a01f to
5ddc227
Compare
Member
|
/azp run ci |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Member
|
/azp run ci |
|
Azure Pipelines successfully started running 1 pipeline(s). |
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 this PR does / why we need it:
In busy regions with concurrent cluster installations, the RP process is being OOM-killed by the kernel when it exceeds its 2GB cgroups limit. During peak load, the RP attempts to use ~2.5GB of memory, which triggers the kernel's OOM killer and causes the process to be terminated.
This PR bumps the 2GB memory to 4GB. This increase is safe since the default RP VMSS SKU is being bumped from Standard_D2s_v3 (8GB) to Standard_D4s_v3 (16GB), providing sufficient headroom for the higher memory limit.
Is there any documentation that needs to be updated for this PR?
no