spinframework / spinframework/spin-operator
Support default config at the namespace level
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 289
- Forks
- 34
- PR merge metrics
- No merged PRs in 30d
Description
Problem
If a user has wants to deploy many SpinApps into their cluster it is likely that a portion of the configuration for each SpinApp will be duplicated. For example you may want to provide runtime config to every single Spin app that configures the CosmosDB instance it should use as a KV provider.
Potential solution
Provide a way to configure default config for a namespace such that any SpinApp in that namespace inherits that default config.
Considerations
- Where would this default config live? On
SpinAppExecutor? On a new CR? Somewhere else? - What configuration would we want to allow to set defaults for. Runtime config seems like an obvious choice. Most of the other fields of the
SpinAppCRD seem like things that would be useful to set defaults for too.
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
The issue names no files, tests, or entry points; begin by surveying the SpinApp CRD and SpinAppExecutor configuration flow. Compare a namespace-level custom resource with executor-owned defaults, then define which SpinApp fields inherit values and how conflicts are resolved.
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