Skip to content

Conversation

ChenYi015
Copy link
Member

Purpose of this PR

Proposed changes:

Change Category

  • Bugfix (non-breaking change which fixes an issue)
  • Feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that could affect existing functionality)
  • Documentation update

Rationale

Checklist

  • I have conducted a self-review of my own code.
  • I have updated documentation accordingly.
  • I have added tests that prove my changes are effective or that my feature works.
  • Existing unit tests pass locally with my changes.

Additional Notes

@jacobsalway
Copy link
Member

/hold

For at least a day or two to gives others a chance to review

Copy link
Member

@jacobsalway jacobsalway left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm
/approve

We've been running the Spark operator internally for ~2 years and I can say I've never used sparkctl. We mainly interact with the the CRs with kubectl or Helm. The only functionality that comes to mind that we should add would be a way to trigger a ScheduledSparkApplication with an annotation.

Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jacobsalway

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@nabuskey
Copy link
Contributor

There might be users who are using sparkctl considering it has been in the repo since 2018. I think it's a better idea to mark it as deprecated to give people time to deal with the removal than to remove it right away. I would mark it deprecated in Cobra and notify users in the next release notes.

@vikas-saxena02
Copy link
Contributor

There might be users who are using sparkctl considering it has been in the repo since 2018. I think it's a better idea to mark it as deprecated to give people time to deal with the removal than to remove it right away. I would mark it deprecated in Cobra and notify users in the next release notes.

@nabuskey @jacobsalway @ChenYi015 I have raised #2484 as per the above suggestion to mark sparkctl deprecated

@ChenYi015
Copy link
Member Author

Since we have already mark sparkctl as deprecated in v2.1.1 release notes and README, I think we can continue on removing it.

@vikas-saxena02
Copy link
Contributor

I second this change/proposal.

@nabuskey
Copy link
Contributor

Sounds good to me. We should adopt a deprecation process going forward though. How many versions must released before removed, etc. Especially with changes coming to webhooks and all, having it established helps in the future. We can point at it when users ask questions around field and feature deprecation. I am happy to work on it if interested.

Signed-off-by: Yi Chen <[email protected]>
Copy link
Member

@jacobsalway jacobsalway left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@google-oss-prow google-oss-prow bot added the lgtm label Apr 21, 2025
@ChenYi015
Copy link
Member Author

/unhold

@google-oss-prow google-oss-prow bot merged commit 836a918 into kubeflow:master Apr 21, 2025
15 checks passed
@ChenYi015 ChenYi015 deleted the remove-sparkctl branch April 21, 2025 06:46
@ChenYi015 ChenYi015 mentioned this pull request May 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Remove sparkctl
4 participants