Add support for KERNEL_VOLUMES and KERNEL_VOLUME_MOUNTS to Spark Operator #1430
Conversation
This file contains hidden or 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
…ator kernel templates
yalindogusahin
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This patch adds support for injecting KERNEL_VOLUMES and KERNEL_VOLUME_MOUNTS into the Spark Operator kernel templates.
Previously, the Spark Operator kernelspec did not include any volumeMounts or volumes sections, so environment variables like KERNEL_VOLUMES and KERNEL_VOLUME_MOUNTS had no effect.
With this change, Enterprise Gateway now correctly propagates these variables into the generated SparkApplication manifest, allowing driver and executor pods to mount shared volumes (e.g. NFS or PVC) defined in the notebook environment.