Sheng Yang

Yes. After the storage created, Kubernetes will always try schedule the pod close to the storage.

@meyerbro Can you provide with the log with the local path provisioner pod? You shouldn't need to create `/opt/local-path-provisioner` manually.

@meyerbro The creation process will create a helper pod on the host to help with setup the directory. It seems the pod doesn't finish after 120 seconds. Can you check...

@meyerbro When you see the `create-` pod started, it will change to `running` later? or is it always in `pending` state? Can you try `kubectl describe` for the pod? Something...

@cruizer Yes, can you create a separate issue? It's clear that your issue is caused by SELinux.

@dick-twocows It's just shown as a timeout from the daemon side. during the time, can you check the helper pod status and why it failed? You should able to see...

@Antonyab It seems you didn't apply the RBAC rule correctly. Can you try to reapply the following part of [yaml](https://github.com/rancher/local-path-provisioner/blob/master/deploy/local-path-storage.yaml)? ``` apiVersion: rbac.authorization.k8s.io/v1 kind: ClusterRole metadata: name: local-path-provisioner-role rules: -...

Might be it got deleted by accident? Probably want to check other components in the yaml if they're still there.

@Antonyab Local path provisioner won't delete the clusterrolebinding. I am almost sure there is something else deleting it, might be some malfunctioned security feature or other app or admin?

Currently, the volume size for the local path provisioned doesn't have a quota, so the size used by the pod can be bigger.