stackabletech / stackabletech/spark-k8s-operator
Implement some form of deletion policy for Spark applications
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 72
- Forks
- 4
- Avg merge
- 2d 15h
- Merged PRs (30d)
- 15
Description
Description
SparkApplications own all resources created by spark-submit, including the driver Pod. Since applications are created by the user, the dependents remain present in the cluster long after the application is finished.
To clean up these (stale) resources, we propose implementing some form of deletion policy for the SparkApplication it's self. Possible policies could be:
NeverAlwaysAlwaysOnSuccess
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
No file, test, or entry point is named. Start by locating the SparkApplication lifecycle and the resources created by spark-submit, including the driver Pod; define the deletion-policy behavior and verify that stale dependents are handled for Never, Always, and AlwaysOnSuccess.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, rust, spark
- Domain
- data-engineering, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100