use new kubeflow repository #23
Closed
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
…ithub.com/spotinst/spark-on-k8s-operator into BGD-5677-update-spark-operator-repository
HafdisE
previously approved these changes
Aug 15, 2024
|
we'll “refork” the repo from upstream |
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
BGD-5677
Description
Use the new kubeflow/spark-operator repository instead of the GoogleCloudPlatform/spark-on-k8s-operator
This is needed to be able to update k8s libraries (in another pr) to fix vulnerabilities.
Demo
Not relevant since not a functional change
Checklist
How to test
No functional change so just run integration tests
Test plan and results
The integration tests ran successfully