pal-e-docs

Review: ArgoCD repo-server memory bump (1 alert)

review-191-2026-03-18 Review

review ready
Project

Verdict: READY

Template Completeness

  • [x] Lineage
  • [x] Repo
  • [x] User Story
  • [x] Context
  • [x] File Targets
  • [x] Acceptance Criteria
  • [x] Test Expectations
  • [x] Constraints
  • [x] Checklist
  • [x] Related

File Targets

  • [x] ~/pal-e-services/terraform/main.tf lines 93-97 — verified: repoServer block exists with requests = { cpu = "50m", memory = "64Mi" } and limits = { memory = "256Mi" }. Exact match to issue description.

Repo Placement

Issue filed on forgejo_admin/pal-e-platform (board repo), but ### Repo correctly states forgejo_admin/pal-e-services where the Helm values live. This is acceptable — platform board tracks cross-repo ops work. Only one repo needs changes.

Dependencies

  • Board item #191 is in todo column, no blockers.
  • Umbrella issue #109 (board item #188, in_progress) identified this alert. #112 is a standalone child ticket.
  • Similar precedent: todo-argocd-image-updater-oom (#162) resolved successfully with same pattern (memory bump).
  • No other board items depend on or are blocked by this ticket.

Acceptance Criteria

All three criteria are verifiable:
  • No OOMKill for 48h — real but requires post-deploy monitoring, not single-session testable. Agent can confirm initial deploy and first hour.
  • kubectl top stays under 512Mi — immediately testable after apply.
  • Alert clears — verifiable via Alertmanager API within ~15 minutes of stable pod.
Test commands are concrete: tofu plan -lock=false, kubectl describe pod, kubectl top pod. All executable by agent.

Blast Radius

  • ArgoCD server component (lines 79-84) has identical 64Mi/256Mi limits. If repo-server OOMs under 8-app load, the API server may face similar pressure under heavy UI/API traffic. Not a blocker for this ticket, but worth monitoring.
  • No downstream consumers affected — this is a memory limit change on a single pod, no config or API changes.
  • The SOPS CMP sidecar (initContainer at lines 98-109) runs alongside repo-server and has its own resource limits (32Mi/128Mi at lines 164-165). The bump only affects the main container.

Recommendation

No action needed. Scope is well-defined, file targets verified, single-file change with clear acceptance criteria. Ready for agent dispatch.