spinframework / spinframework/spin-operator
Can we give better errors in spinapp status?
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 289
- Forks
- 34
- PR merge metrics
- No merged PRs in 30d
Description
Context: https://discord.com/channels/926888690310053918/950022897160839248/1275126957322801192 and https://www.youtube.com/watch?v=2CFj4_wt2qo&t=3609s
They were attempting to deploy a Wasm OCI artifact which is not yet directly supported by Spin.
Currently they just get the standard k8s "Deployment does not have minimum availability" status, but I wonder if we could give more useful feedback, especially when the app configuration has fatal errors.
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 the spinapp status handling and the Kubernetes Deployment availability status described in the issue. Reproduce the Wasm OCI artifact case and inspect how fatal application-configuration errors are surfaced; done means status reports actionable feedback instead of only the generic minimum-availability message.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes, wasm
- Domain
- cli, devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 32/100