chore(deploy): expose resources/nodeOptions, lower staging memory#2954
chore(deploy): expose resources/nodeOptions, lower staging memory#2954
Conversation
Parameterize resources and NODE_OPTIONS in the website chart so each environment can size its own pod. Staging now requests/limits 500Mi with --max-old-space-size=384; production keeps 1Gi/768. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Greptile SummaryThis PR parameterizes the previously hardcoded Confidence Score: 5/5Safe to merge — production values are unchanged, Helm templating is correct, and the staging overlay is a deliberate, well-scoped reduction. No logic errors, no security concerns, and no behavioral changes for production. The refactoring is minimal and uses established Helm idioms. Staging is the only environment that gets different resource values. No files require special attention. Important Files Changed
Reviews (1): Last reviewed commit: "chore(deploy): expose resources and node..." | Re-trigger Greptile |
Summary
resourcesblock andNODE_OPTIONSenv in the website Helm chart so each environment can size its own pod--max-old-space-size=768--max-old-space-size=384to match the smaller heapTest plan
helm templaterenders production values to current 1Gi / 768 settingshelm templatewith staging overlay renders 500Mi / 384/healthzunder the lower limit🤖 Generated with Claude Code