kubeflow/sdk

SparkConnect CR cleanup behavior on failure and SDK state mismatch

Open

#476 opened on Apr 30, 2026

View on GitHub
 (5 comments) (1 reaction) (0 assignees)Python (196 forks)auto 404
area/sparkgood first issuehelp wantedkind/bug

Repository metrics

Stars
 (124 stars)
PR merge metrics
 (PR metrics pending)

Description

Summary

While working on port-forward cleanup in the SDK #460 , it surfaced that there may be a broader gap in how SparkConnect resources are handled on failure.

Observations

  • SparkConnect CR does not appear to clean up resources when connection/setup fails
  • This can leave resources running if failure happens mid-connection

There is a related issue in the Spark Operator: kubeflow/spark-operator#2927

Additional Observation

There also appears to be a mismatch in state mapping:

  • The SDK exposes a "Running" state
  • SparkConnect CR does not expose a corresponding state

Contributor guide

Research direction
Investigate the SparkConnect CR lifecycle and SDK state mapping code to identify where cleanup is missing on failure and where state mapping differs.
Tech stack
pythonkubernetes
Domain
backenddevops
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
GitPython
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60