Allow configuration of the controler resources and limits in helm chart

[knechtionscoding]

Hi! Trying to install kelos via gitops and the controller is being oom killed. Right now the controller resources aren't exposed in the chart values.yaml and likely should.

[kelos-bot]

🤖 Kelos Task Status

Task kelos-triage-779 has succeeded. ✅

[kelos-bot]

🤖 Kelos Agent @gjkim42

Kelos Triage Report

Kind: kind/feature
Priority: priority/important-soon — Controller OOM kills block adoption; the 128Mi hardcoded memory limit is too low for real workloads
Actor: actor/kelos — Clear scope: add resource request/limit fields to values.yaml and template them into the controller deployment

Status: STILL VALID

Evidence:

• The controller deployment template (internal/manifests/charts/kelos/templates/deployment.yaml:97-103) hardcodes resources: cpu: 500m / memory: 128Mi limits, cpu: 10m / memory: 64Mi requests — with no Helm values override
• values.yaml already exposes spawnerResourceRequests/Limits and tokenRefresherResourceRequests/Limits but has no equivalent for the controller
• No merged PRs or commits reference this issue — it has not been addressed
• The fix should follow the existing pattern used for spawner/tokenRefresher resource configuration

Duplicates found: None found

Recommendation: KEEP OPEN