How do I fix the pod has unbound immediate PersistentVolumeClaims?
To solve your problem:
- Provide a PersistentVolume that meets the constraints of the claim (a size >= 100Mi)
- Either remove the storage class from PersistentVolumeClaim or provide an empty value ( “” )
- Remove StorageClass from your cluster.
If the error message indicates that the pod has independent immediate PersistentVolumeClaims (PVC), then the pod cannot create its persistent volume.
Table of Contents
How to resolve volume node affinity conflict?
To fix this, create a storage class for a single zone and use that storage class on your PVC. After patching the node with the tags, the “1 node(s) had volume node affinity conflict” error disappeared, so PV, PVC with a pod were successfully deployed. The value of these tags is specific to the cloud provider.
What has volume node affinity conflict in AWS?
The “volume node affinity conflict” error occurs when the persistent volume claims that the pod is scheduled to different zones, rather than one zone. Therefore, the actual pod cannot be scheduled because it cannot connect to the volume from another zone.
Hi, I tried to do helm install stable/postgresql. but it gave me “pod has triggered immediate PersistentVolumeClaims” using minikube v0.35.0, it worked fine before on minikube v0.33 (tried redis and mysql chart too, gave same error). I reinstalled minikube. Also, I tried to start with new minikube. I don’t understand where I’m doing it wrong.
If that’s the case, you will definitely get an immediate unbound error PersistentVolumeClaims no volume plugin matches name 3. The total number of PVCs (Persistent Volume Claim) is greater than PV (Persistent Volume) The third possible test case can be where total number of PVCs > total number of PVs
When does persistent volume remain unbound in Kubernetes?
PersistentVolumeClaims will remain unbound indefinitely if no matching PersistentVolume exists. PersistentVolume is compared against accessModes and capacity . In this case, the capacity of the PV is 10 Gi, while the PVC has a capacity of 3 Gi.
Why is persistent volume driver not bound to PV?
The mentioned error can be due to various reasons; below are some options i found. The persistent volume driver could not find a PV with a capacity size equal to or greater than the value that was specified on the PVC. If PV capacity >= PVC capacity, then PVC should be linked to PV.