-
Notifications
You must be signed in to change notification settings - Fork 67
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Host share on example pod is lost when s3-provider is restarted #5
Comments
Tested, works |
perfect. Thanks for your feedback. |
There is no subpath feature in kubernetes volume section. My version is Error while starting the daemon
The issue still persists and i have to unmount the hostpath everytime to get it working. |
kubernetes 1.14 is not supported for this. We use 1.19.2 |
Subpath are for volumeMounts right as mentioned here ?
But not for volumes as specified above. |
It you set the host share to the same path as the mountpoint oh the host, if the host remounts the fuse volume, the example pod looses the folder link and gets
Transport endpoint is not connected
The workaround I found was to mount on the example pod a folder up the tree, and then that folder remains static and does not get a different mapping if the fuse gets remounted. That way the folder remains in place and the subfolder that mounted has its node updated correctly.
Ideally you would want something like
I am not sure if that is a feature available in Kubernets. will test.
The text was updated successfully, but these errors were encountered: