stackabletech / stackabletech/spark-k8s-operator
Improve operator stability
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 72
- Forks
- 4
- Avg merge
- 2d 15h
- Merged PRs (30d)
- 15
Description
As a user of the spark-k8s-operator I want to be able to rely on my operator to discontinue reconciliation attempts and to clean up pods from finished jobs after a defined TTL.
- define retry limit for job (init-job, driver and executor)
- configure TTL for job and driver pods for clean up?
- controller stops responding for indeterminate reasons (not does not reconcile)
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 reconciliation for the init job, driver, and executor, then inspect how finished jobs and driver pods are cleaned up. Define the expected retry limit, TTL behavior, and response when reconciliation becomes indeterminate; the work is done when these cases stop retrying indefinitely and cleanup follows the configured TTL.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, rust, spark
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100