Context

Slack thread: https://slack.com/archives/C034XCYJPSN/p1770701104014179

Problem

Users setting up resources for the Kubernetes operator and Helm chart deployments lack guidance on CPU/memory requests and limits. The current guidance is suboptimal and does not recommend setting requests equal to limits, which can lead to inconsistent scheduling and resource contention.

Suggested Fix

• Add a dedicated section in the k8s operator resource setup and Helm chart deployment docs that explicitly recommends setting requests = limits for both CPU and memory.
• Provide a short rationale for why requests should equal limits in this context.
• Include a concise configuration example showing the recommended values for both CPU and memory.
• Ensure the recommendation appears in any resource-related tables or defaults documentation for these deployment paths.