Difference between revisions of "Pod has unbound immediate PersistentVolumeClaims"
Jump to navigation
Jump to search
| Line 11: | Line 11: | ||
== See also == | == See also == | ||
| − | * {{ | + | * {{FailedScheduling}} |
| + | * {{PVC}} | ||
[[Category:GKS]] | [[Category:GKS]] | ||
Revision as of 16:20, 12 December 2023
default 18m Warning FailedScheduling pod/sentry-web-79b8bbccdf-r2qr4 0/4 nodes are available: 4 pod has unbound immediate PersistentVolumeClaims.
19m Warning FailedScheduling pod/kotsadm-minio-0 0/1 nodes are available: pod has unbound immediate PersistentVolumeClaims. preemption: 0/1 nodes are available: 1 No preemption victims found for incoming pod..
Pod has unbound immediate PersistentVolumeClaims
See also
- FailedScheduling:
Insufficient cpu,Insufficient memory,timed out waiting for the condition,unbound immediate PersistentVolumeClaims - Kubernetes Persistent Volume Claim (PVC) (
kind: PersistentVolumeClaim), Kubernetes Persistent volumes (PV)(kind: PersistentVolume),kubectl describe pvc, kubectl get pvc, ClaimLost, ProvisioningSucceeded, PV access control
Advertising:
