stackabletech / stackabletech/spark-k8s-operator
Add driver information to the application status
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 72
- Forks
- 4
- Avg merge
- 2d 15h
- Merged PRs (30d)
- 15
Description
Description
Tools (most notably Airflow) that manage the lifecycle of SparkApplications need to be able to monitor the logs of the application driver.
Currently there is no reference to the driver Pod from the application, which makes the task from above more cumbersome than it should be.
The operator should include such a reference in the SparkApplication status, to enable tools like Airflow's Kubernetes sensor to work out of the box.
Investigate if it's possible to persist logs from k8s executors and spark pods and update the the documentation page accordingly.
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 how the SparkApplication status is defined and updated, then inspect how the Kubernetes driver Pod is identified. Review the linked Airflow documentation page and determine what executor and Spark pod log persistence behavior needs documenting. Done means the status exposes the driver reference and the documentation reflects the supported log behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, rust
- Domain
- distributed-systems, documentation, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100