spinframework / spinframework/spin-operator
Determine reasonable defaults for Spin Operator pod cpu/mem resources
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 289
- Forks
- 34
- PR merge metrics
- No merged PRs in 30d
Description
Decide on default/baseline cpu/mem configuration for the Spin Operator.
Main operator container: https://github.com/fermyon/spin-operator/blob/main/config/manager/manager.yaml#L92-L100
and kube-rbac-proxy: https://github.com/fermyon/spin-operator/blob/main/config/default/manager_auth_proxy_patch.yaml#L28-L34
I'm assuming we'll want to ensure the defaults are friendly to resource-constrained or small-footprint clusters (minikube, kind, k3d).
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 with config/manager/manager.yaml lines 92-100 and config/default/manager_auth_proxy_patch.yaml lines 28-34 to inspect the current resource settings for the main operator and kube-rbac-proxy containers. Compare the needs of both containers with the stated minikube, kind, and k3d constraints; done means agreed baseline CPU and memory defaults are documented in those configuration locations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100