bump spark-operator chart version #229
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
alextarasov-spot
approved these changes
Sep 11, 2024
alextarasov-spot
deleted the
BGD-5677-spark-operator-security-patching-effort
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Jira ticket
https://spotinst.atlassian.net/browse/BGD-5677
Description
Spark operator security patching involving library updates and related code change
Checklist
How to test
With this version of the Spark operator running in the DP
Launch a Spark application via Postman (such as the SparkConnect one)
Launch a new Spark application from a workspace notebook.
Try deleting a running Spark application
Test plan and results
Both the Spark application and the Notebook application ran successfully. Spark application deletion works as well