You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Dongjoon Hyun (Jira)" <ji...@apache.org> on 2020/03/16 22:53:04 UTC
[jira] [Updated] (SPARK-28905) PVs mounted into Spark may not be
writable by Spark
[ https://issues.apache.org/jira/browse/SPARK-28905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dongjoon Hyun updated SPARK-28905:
----------------------------------
Affects Version/s: (was: 3.0.0)
3.1.0
> PVs mounted into Spark may not be writable by Spark
> ---------------------------------------------------
>
> Key: SPARK-28905
> URL: https://issues.apache.org/jira/browse/SPARK-28905
> Project: Spark
> Issue Type: Improvement
> Components: Kubernetes
> Affects Versions: 3.1.0
> Reporter: Holden Karau
> Assignee: Holden Karau
> Priority: Minor
>
> Right now, for Spark to have write access to the PVs we provide it, they need to be created with UID 185. This _may_ be a feature, but if we wanted to make this more flexible we could set a FsGroup in our security context when setting up the volumes. This would give Spark access provided the PV supports fsgroup (which on minikube does not appear to be the case - [https://github.com/kubernetes/minikube/issues/1990] )
>
> If we did want to do this we could add the securitygroup in MountVolumesFeatureStep but I don't know if we want to do this or if the current behaviour is desired.
> I ran into this while getting the integration tests to work w/minikube 1.3.1 on OSX. See https://issues.apache.org/jira/browse/SPARK-28904 for details.
>
> cc [~ifilonenko] for thoughts
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org