You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Eric Carlson (JIRA)" <ji...@apache.org> on 2018/12/15 04:05:00 UTC
[jira] [Comment Edited] (SPARK-26342) Support for NFS mount for
Kubernetes
[ https://issues.apache.org/jira/browse/SPARK-26342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16721990#comment-16721990 ]
Eric Carlson edited comment on SPARK-26342 at 12/15/18 4:04 AM:
----------------------------------------------------------------
(discussion also applies for flexvolume improvement request SPARK-26344)
Hi [~liyinan926] - that's right that pod templates can be used for this, and I have that working, but it would be more convenient for users if a separate yaml didn't have to be crafted for some options when so much is already available via the conf mechanisms.
I actually already have this code working on a local branch, waiting for corporate contributor approval to publish for review - it doesn't really add a feature, just adds the nfs (and in a separate branch, flexvolume) types to the existing volume config options, which ends up being a fairly small addition to a few switch statements.
Would a change like this be up for consideration, or is there a design decision to not add beyond empytdir, pvc, and hostpath? (I couldn't find design docs/discussion)
was (Author: ektar):
(discussion also applies for flexvolume improvement request)
Hi [~liyinan926] - that's right that pod templates can be used for this, and I have that working, but it would be more convenient for users if a separate yaml didn't have to be crafted for some options when so much is already available via the conf mechanisms.
I actually already have this code working on a local branch, waiting for corporate contributor approval to publish for review - it doesn't really add a feature, just adds the nfs (and in a separate branch, flexvolume) types to the existing volume config options, which ends up being a fairly small addition to a few switch statements.
Would a change like this be up for consideration, or is there a design decision to not add beyond empytdir, pvc, and hostpath? (I couldn't find design docs/discussion)
> Support for NFS mount for Kubernetes
> ------------------------------------
>
> Key: SPARK-26342
> URL: https://issues.apache.org/jira/browse/SPARK-26342
> Project: Spark
> Issue Type: Improvement
> Components: Kubernetes
> Affects Versions: 2.4.0
> Reporter: Eric Carlson
> Priority: Minor
>
> Currently only hostPath, emptyDir, and PVC volume types are accepted for Kubernetes-deployed drivers and executors. Possibility to mount NFS paths would allow access to a common and easy-to-deploy shared storage solution.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org