Difference between revisions of "VolumeBinding"
Jump to navigation
Jump to search
| Line 25: | Line 25: | ||
== See also == | == See also == | ||
| − | * {{ | + | * {{K8s sto}} |
[[Category:Kubernetes]] | [[Category:Kubernetes]] | ||
Revision as of 13:00, 27 December 2022
default 8m51s Warning FailedScheduling pod/myprometheus-alertmanager-5967d4ff85-5glkh running PreBind plugin "VolumeBinding": binding volumes: timed out waiting for the condition
kubectl get pvc NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE myprometheus-alertmanager Pending gp2 58m myprometheus-server Pending
Related
helm install myprometheus prometheus-community/prometheusaws iam list-open-id-connect-providerskubectl get pvc
we are getting this error because of our Kubernetes node server are less memory what we requesting in ymal file
in Prometheus values.ymal they mentions 8Gi, so we are getting this error
See also
- Kubernetes storage, storage classes, PersistentVolume (PV), PVC, CSI,
kind: StorageClass, kind: PersistentVolumeClaim, kind: PersistentVolume,kubectl [ get | describe | edit ] pvc,volumeClaimTemplates:,kubectl patch pv,FailedMount, Volume Expansion, Volume Cloning, snapshots, ExtraVolumes, NotTriggerScaleUp,volumePVCDataSource, AllowVolumeExpansion, EKS storage, provisioner, Storage Capacity Tracking,VolumeBinding, VolumeClaimTemplate, storage.k8s.io, CKA Storage, DoKC, EmptyDir, Volume populators,storageclass.kubernetes.io
Advertising:
