docs: Reduce wave resource requirements in installation manifests

[bebosudo]

While developing the wave chart, I noticed that wave recommends quite a large amount of resources.

[Copilot]

Pull request overview

Reduces the documented resource allocations for Wave in the Kubernetes and Docker Compose installation guides to better reflect lower recommended requirements.

Changes:

• Lower Wave pod/container memory allocations in Kubernetes and Docker Compose examples.
• Adjust Docker Compose CPU reservation for the Wave service.
• Clean up trailing whitespace in the ECR IAM policy snippet.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.

File	Description
docs/install/kubernetes.md	Lowers memory requests/limits in the Deployment example; minor formatting cleanup in the IAM policy snippet.
docs/install/docker-compose.md	Lowers memory limits/reservations and adjusts CPU reservation in the Docker Swarm/Compose example.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[gwright99]

I've been doing some Wave attribute work over the past few days. Came across this:

wave.cache.digestStore.maxWeightMb
Maximum heap memory (in MB) allocated to the in-memory digest-to-manifest cache used by the registry proxy. Increase this for deployments with high proxy throughput. Warning: Setting this too high can cause memory pressure on the Wave JVM. (NOTE: Description from Claude (not yet validated with human))

Since you are reducing the amount of RAM given to the pod, does the default value of 350MB need to be modified at all?

@munishchouhan @bebosudo

[munishchouhan]

I've been doing some Wave attribute work over the past few days. Came across this:

wave.cache.digestStore.maxWeightMb
Maximum heap memory (in MB) allocated to the in-memory digest-to-manifest cache used by the registry proxy. Increase this for deployments with high proxy throughput. Warning: Setting this too high can cause memory pressure on the Wave JVM. (NOTE: Description from Claude (not yet validated with human))

Since you are reducing the amount of RAM given to the pod, does the default value of 350MB need to be modified at all?

@munishchouhan @bebosudo

this size works in our prod, so should be fine no need to change, we are making k8s and docker requirements as close as possible heap size should not be affected by this