Skip to content

chore(deploy): expose resources/nodeOptions, lower staging memory#2954

Merged
loks0n merged 1 commit intomainfrom
feat/staging-requests
May 1, 2026
Merged

chore(deploy): expose resources/nodeOptions, lower staging memory#2954
loks0n merged 1 commit intomainfrom
feat/staging-requests

Conversation

@loks0n
Copy link
Copy Markdown
Member

@loks0n loks0n commented May 1, 2026

Summary

  • Parameterize the resources block and NODE_OPTIONS env in the website Helm chart so each environment can size its own pod
  • Default values keep production at 1Gi memory (request+limit) with --max-old-space-size=768
  • Staging fra1 now runs at 500Mi (request+limit) with --max-old-space-size=384 to match the smaller heap

Test plan

  • helm template renders production values to current 1Gi / 768 settings
  • helm template with staging overlay renders 500Mi / 384
  • Staging pod starts and serves /healthz under the lower limit

🤖 Generated with Claude Code

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-apps
Copy link
Copy Markdown
Contributor

greptile-apps Bot commented May 1, 2026

Greptile Summary

This PR parameterizes the previously hardcoded resources block and NODE_OPTIONS environment variable in the website Helm chart, moving production defaults into values.yaml and adding a staging-specific overlay in fra1.values.yaml that halves the memory allocation to 500Mi with a matching 384MB V8 heap size. The Helm templating uses the standard toYaml | nindent and | quote patterns correctly, and the default values are identical to what was previously hardcoded — no production behavior changes.

Confidence Score: 5/5

Safe 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

Filename Overview
deploy/website/templates/website.yaml Parameterizes resources block and NODE_OPTIONS env var via Helm values; uses standard `toYaml
deploy/website/values.yaml Adds default resources (1Gi memory, 500m CPU request) and nodeOptions (768MB heap) matching the previously hardcoded production values.
deploy/website/environments/staging/fra1.values.yaml Adds staging-specific resource override: 500Mi memory request/limit and 384MB V8 heap, consistent with the smaller allocation.

Reviews (1): Last reviewed commit: "chore(deploy): expose resources and node..." | Re-trigger Greptile

@loks0n loks0n merged commit dea7a35 into main May 1, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant