why need global mount in volume manager

[mjaow]

i find it's confused to add global mount to volume manager.The code says it mount device to global mount path then mount the volume to pod specific path.Does it really need global mount?Why not just mount device to pod specific path?I think it also works fine

[k8s-github-robot]

@mjaow
There are no sig labels on this issue. Please add a sig label by:

1. mentioning a sig: @kubernetes/sig-<group-name>-<group-suffix>
   e.g., @kubernetes/sig-contributor-experience-<group-suffix> to notify the contributor experience sig, OR

2. specifying the label manually: /sig <label>
   e.g., /sig scalability to apply the sig/scalability label

Note: Method 1 will trigger an email to the group. You can find the group list here and label list here.
The <group-suffix> in the method 1 has to be replaced with one of these: bugs, feature-requests, pr-reviews, test-failures, proposals

[mjaow]

/sig storage
@saad-ali
@childsb

[wongma7]

because the device can be mounted only once and so if >1 pods want to use it, we then bind-mount it to the pod-specific paths

[mjaow]

@wongma7 ,thx i get it