search

rancher / local-path-provisioner

Dynamically provisioning persistent local storage with Kubernetes
Apache License 2.0
2.07k stars 439 forks source link

Volume not provisioned when binding type is set to `Immediate` #386

Closed roshanirathi closed 1 month ago

roshanirathi commented 4 months ago

PVC is in pending state with error - configuration error, no node was specified. This behaviour is seen only when binding type is set to Immediate. Volume gets provisioned when set to WaitForFirstConsumer.

As per what I have read online, the reason for this is PodSecurityPolicy was not updated to use local-path. But since PSP is deprecated, what is the alternative solution for it?

I tried adding namespace labels for ns in which the LPP was deployed and also for the ns in which the PVC was deployed, but that didn't work out.

Versions used: LPP - 0.25.0 k8s - 1.28.5

shkatara commented 3 months ago

Hi Roshni, I am also getting the same issue. Did you have any luck so far ?

MisderGAO commented 3 months ago

Hello, Same issue for me. community k8s 1.28.7

roshanirathi commented 3 months ago

Adding node-affinity in persistent volume spec is one way to get it working. But then it negates the entire point of dynamic provisioning.

github-actions[bot] commented 1 month ago

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

github-actions[bot] commented 1 month ago

This issue was closed because it has been stalled for 5 days with no activity.

jackson-chris commented 2 weeks ago

Can maintainers confirm or deny if using a VolumeBindingMode of Immediate is currently supported?