Christian Mesh

@yuvipanda I'd like to be a guinea pig on this. I am trying to setup a persistent EFS volume and use that as the user storage. So far I've created...

1. I saw that, thanks for the clearer explanation 2. I don't think that anonuid/gid is an option on EFS I'll take a look through the nfs-flex-volume repo

I am currently getting the following response: ``` HTTP response body: {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"Pod in version \"v1\" cannot be handled as a Pod: v1.Pod: Spec: v1.PodSpec: Containers: []v1.Container: v1.Container: VolumeMounts: []v1.VolumeMount: v1.VolumeMount:...

Ok, I've got the mount working. I did not do the label stuff yet, simply set 'storageClassName: ""' in the claim. That seemed to work just fine. I ran into...

EFS Success! Process: Setup an EFS volume. It must be in the same VPC as your cluster. This can be changed in the AWS settings after it has been created....

Could we add the chown hack I put in my image to the start.sh script in the stacks repo? https://github.com/jupyter/docker-stacks/blob/master/base-notebook/start.sh#L19 Would that break any existing users setups?

I figure doing the chown ourselves resolves it for now (behind a config setting) and can be removed once K8S finalizes if/how/when the subpath permissions should be set

``` singleuser: image: name: jupyter/base-notebook tag: 29b68cd9e187 extraEnv: CHOWN_HOME: 'yes' ``` Just confirmed the fix in my test env

Either should work, though I'd recommend a clean install just to be safe.

We are currently doing an internal alpha with a setup similar to the one mentioned above and working out any minor issues which come up. @mfox22 I'd be up for...