stackabletech / stackabletech/spark-k8s-operator
better/more debugging options
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 72
- Forks
- 4
- Avg merge
- 2d 15h
- Merged PRs (30d)
- 15
Description
Description
The Spark-k8s pods dies immediatly after executing. For debugging purposes and checking configuration it would be helpful if the pod of the driver could stay alive. Something like an option e.g. for sleep infinity.
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
The issue names no files or tests. Start by locating the Spark-k8s driver pod configuration and the operator entry point that handles driver lifecycle; then determine where a debugging option could be exposed. Done means users can keep the driver pod alive after execution, with the behavior covered by an appropriate test or documented verification.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, rust
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100