Difference between revisions of "VolumeBinding"

From wikieduonline
Jump to navigation Jump to search
 
(5 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 7: Line 9:
  
 
  [[kubectl get]] [[pvc]]
 
  [[kubectl get]] [[pvc]]
  NAME                        STATUS    VOLUME  CAPACITY  ACCESS MODES  STORAGECLASS  AGE
+
  NAME                        STATUS    VOLUME  CAPACITY  ACCESS MODES  [[STORAGECLASS]]   AGE
  myprometheus-alertmanager  Pending                                      gp2            58m
+
  myprometheus-alertmanager  Pending                                      [[gp2]]           58m
 
  myprometheus-server        Pending     
 
  myprometheus-server        Pending     
  
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>
we are getting this error because of our Kubernetes node server are less memory what we requesting in ymal file
+
* [[Kubernetes scheduling]]
 
 
in Prometheus values.ymal they mentions 8Gi, so we are getting this error
 
 
 
 
 
* [[Scheduling]]
 
  
 
== See also ==
 
== See also ==

Latest revision as of 11:55, 12 January 2024

Advertising: