Tune website CPU and memory resources

[loks0n]

Summary

• Increase cpu request from 400m to 500m
• Raise memory request and limit from 512Mi to 1Gi
• Bump Node --max-old-space-size from 400 to 768

Test plan

• Verify deployment rolls out successfully in staging
• Confirm pods stay within new memory limit under normal load

🤖 Generated with Claude Code

[greptile-apps]

Greptile Summary

Tunes the website Kubernetes deployment by bumping CPU requests from 400m to 500m, doubling the memory request and limit from 512Mi to 1Gi, and raising the Node.js --max-old-space-size from 400 to 768 MB. The heap ceiling (768 MB) is ~75% of the container memory limit (1024 MiB), leaving roughly 256 MiB for off-heap allocations and OS overhead, which is a sound ratio.

Confidence Score: 5/5

Safe to merge — clean resource-tuning change with no logic modifications.

Single-file infra change with proportionally correct values: heap size is 75% of the memory limit (standard guidance), CPU request increase is modest, and no CPU limit is added (intentional, avoids throttling). No code logic is touched.

No files require special attention.

Important Files Changed

Filename	Overview
deploy/website/templates/website.yaml	Increases CPU request (400m→500m), doubles memory request/limit (512Mi→1Gi), and raises Node.js heap ceiling (400→768 MB) — all proportionally aligned.

_{Reviews (1): Last reviewed commit: "Tune website CPU and memory resources" | Re-trigger Greptile}