Difference between revisions of "VolumeBinding"
Jump to navigation
Jump to search
(2 intermediate revisions by one other user not shown) | |||
Line 1: | Line 1: | ||
− | default 8m51s Warning FailedScheduling pod/myprometheus-alertmanager-5967d4ff85-5glkh running [[PreBind]] plugin "VolumeBinding": binding volumes: [[timed out waiting for the condition]] | + | |
+ | [[helm install prometheus]] | ||
+ | default 8m51s Warning FailedScheduling pod/myprometheus-[[alertmanager]]-5967d4ff85-5glkh running [[PreBind]] plugin "VolumeBinding": binding volumes: [[timed out waiting for the condition]] | ||
Line 16: | Line 18: | ||
* <code>[[aws iam list-open-id-connect-providers]]</code> | * <code>[[aws iam list-open-id-connect-providers]]</code> | ||
* <code>[[kubectl get pvc]]</code> | * <code>[[kubectl get pvc]]</code> | ||
+ | * <code>[[kubectl get events]]</code> | ||
* [[Kubernetes scheduling]] | * [[Kubernetes scheduling]] | ||
Latest revision as of 11:55, 12 January 2024
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[edit]
helm install myprometheus prometheus-community/prometheus
aws iam list-open-id-connect-providers
kubectl get pvc
kubectl get events
- Kubernetes scheduling
See also[edit]
- 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: