spinframework / spinframework/spin-operator
Decide if spin-operator should be a global or namespaced operator
Open
Nobody has claimed this yet.
needs discussion
- Dominant language
- Go
- Stars
- 289
- Forks
- 34
- PR merge metrics
- No merged PRs in 30d
Description
Currently the spin-operator acts globally (you can apply your SpinApps into any namespace). But, our SpinAppExecutors are namespaced (they need to be in the same namespace as your SpinApp).
We need to decide if we want the spin-operator to be a global or namespaced operator.
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
Review how the spin-operator currently applies SpinApps across namespaces and how namespaced SpinAppExecutors are constrained. Compare the implications of a global versus namespaced operator, then document the decision and its required follow-up changes; the issue is done when the operator scope is explicitly decided.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100