spinframework / spinframework/spin-operator
Increase helm chart memory resource defaults
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 289
- Forks
- 34
- PR merge metrics
- No merged PRs in 30d
Description
https://github.com/spinframework/spin-operator/blob/c5335f2b672acd902761b6661d8e43eebe23d718/charts/spin-operator/values.yaml#L36 specifies a resources.limits.memory: 128Mi. This appears to be too low now, at least on certain platforms (ubuntu amd64, k3s 1.36.2). 128Mi quite reliably produces OOMKilled pods.
It should be increased to at least 256Mi, or maybe even higher. This is, after all, the limit, not the minimum reserved. It would also suggest that resource.requests.memory should also be higher than 128Mi (currently 64Mi), given we know that with 128Mi even a single hello-rust example spinapp can get the operator OOMKilled.
Discussion: https://cloud-native.slack.com/archives/C06PC7JA1EE/p1782522187619599
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at charts/spin-operator/values.yaml#L36 and inspect the default resources block, including the 64Mi memory request. Compare the reported OOMKilled behavior and platform context with the proposed defaults; done means the chart's default request and limit are increased to agreed values and the rendered chart reflects them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 76/100