stackabletech / stackabletech/spark-k8s-operator
SparkApplication shouldn't delete until the pods have been deleted
Open
Nobody has claimed this yet.
type/bug
- Dominant language
- Rust
- Stars
- 72
- Forks
- 4
- Avg merge
- 2d 15h
- Merged PRs (30d)
- 15
Description
Affected Stackable version
24.7.0
Affected Apache Spark-on-Kubernetes version
N/A
Current and expected behavior
When deleting a SparkApplication, the resource shouldn't be deleted until the child resources have been cleaned up by the operator.
Possible solution
Add finalizers to SparkApplication's, and remove them after cleanup is done.
Additional context
Noticed during demo testing before 24.11.
Environment
Client Version: v1.31.0
Kustomize Version: v5.4.2
Server Version: v1.31.2
Would you like to work on fixing this bug?
maybe
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 or test is named. Start by tracing SparkApplication deletion and the operator's child-resource cleanup path; the work is done when deletion retains the SparkApplication until its pods and other child resources have been cleaned up.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, rust, spark
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100