Support for jobs with bounded input
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 581
- Forks
- 153
- PR merge metrics
- No merged PRs in 30d
Description
Currently the operator assumes that a job remains in RUNNING state, and doesn't complete. If the job has bounded input and finishes, then the operator fails do delete the application, trying to take a savepoint. It is possible to set Delete Mode: None, but it would be better to have explicit support for such jobs (and support batch use cases in general).
Contributor guide
No contributing guide indexed for this repository
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 by tracing how the operator handles deletion for jobs that have completed and where it attempts to take a savepoint. Done means bounded-input jobs can be explicitly supported without a failed savepoint, with the intended batch-use behavior defined and verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- distributed-systems, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100