stackabletech / stackabletech/spark-k8s-operator
Clean up orphaned driver pods after #758 is installed
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 72
- Forks
- 4
- Avg merge
- 2d 15h
- Merged PRs (30d)
- 15
Description
Affected Stackable version
dev
Affected Apache Spark-on-Kubernetes version
No response
Current and expected behavior
Currently, after we have merged https://github.com/stackabletech/spark-k8s-operator/pull/758, driver pods which ran prior to this fix won't be cleaned up as they miss the owner reference.
The error loop is caused by the nature of a STS being immutable apart of replicas, template and updateStrategy.
Possible solution
No response
Additional context
No response
Environment
No response
Would you like to work on fixing this bug?
None
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 reviewing PR #758 and the StatefulSet reconciliation path for driver pods, focusing on how previously created pods lack an owner reference. Confirm the cleanup behavior for those orphaned pods and ensure reconciliation no longer enters the reported error loop; the fix is complete when old driver pods are cleaned up after the update is installed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, rust, spark
- Domain
- devops, distributed-systems, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100