Reduce dependency on values.yaml file for requests proxy

[saqlainsyed007]

Summary

Related

Type of change

• Feature
• Bug fix
• Tech-debt / refactor
• Docs
• Security / hardening
• Breaking change

Test plan

Screenshots / recordings

Deployment notes

Checklist

• Tests added / updated and passing locally
• Docs updated if behavior or config changed
• No secrets / credentials in the diff
• For security-sensitive paths: appropriate reviewer requested

---

Note

Medium Risk
Changes requests-proxy deployment defaults by hardcoding CPU/memory and forcing imagePullPolicy: Always, which can affect scheduling and rollout/pull behavior across clusters.

Overview
requests-proxy’s Helm template now hardcodes its CPU/memory requests+limits and sets imagePullPolicy: Always, rather than reading resource settings (or pull policy) from values.yaml.

The image digest lookup is also made more defensive by using dig "requestsProxy" "digest" against .Values.images, and the resources.requestsProxy block is removed from client/values.yaml.

^{Reviewed by Cursor Bugbot for commit 60387e1. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes and found 2 potential issues.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit b430479. Configure here.}