spinframework / spinframework/spin-operator
allow default executor without spinappexecutor resource applied
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 289
- Forks
- 34
- PR merge metrics
- No merged PRs in 30d
Description
It would be nice if we could default to using containerd-shim-spin as the default executor without having to install of configure the SpinAppExecutor resource and we could use SpinAppExecutor as a means for extending to other executors as well as configuring non-default values ( ex. using a non-default name for the executor, using a non-default runtimeClassName)
We've had this convo before I believe but I still go back to wanting this experience mostly because it's a few less steps and potential errors in the quickstart workflow.
The SpinApp "simple-spinapp" is invalid: spec.executor: Invalid value: "containerd-shim-spin": executor does not exist on cluster
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
No implementation files or tests are named. Start by tracing how SpinApp executor validation discovers SpinAppExecutor resources and follow the quickstart workflow that produces the reported error. Done means the default executor works without that resource while SpinAppExecutor still supports alternate executors and non-default values.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes, wasm
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100