Difference between revisions of "Aws-ebs-csi-driver"

From wikieduonline
Jump to navigation Jump to search
Line 10: Line 10:
 
  default 8m51s      Warning  [[FailedScheduling]]      pod/myprometheus-alertmanager-5967d4ff85-5glkh    running [[PreBind plugin]] "[[VolumeBinding]]": binding volumes: [[timed out waiting for the condition]]
 
  default 8m51s      Warning  [[FailedScheduling]]      pod/myprometheus-alertmanager-5967d4ff85-5glkh    running [[PreBind plugin]] "[[VolumeBinding]]": binding volumes: [[timed out waiting for the condition]]
 
  default    4m58s      Normal    [[ExternalProvisioning]]  persistentvolumeclaim/myprometheus-alertmanager  [[waiting for a volume to be created, either by external provisioner]] "[[ebs.csi.aws.com]]" or manually created by system administrator
 
  default    4m58s      Normal    [[ExternalProvisioning]]  persistentvolumeclaim/myprometheus-alertmanager  [[waiting for a volume to be created, either by external provisioner]] "[[ebs.csi.aws.com]]" or manually created by system administrator
 
 
The in-tree StorageClass provisioner is named <code>[[kubernetes.io/aws-ebs]]</code>. The Amazon EBS CSI [[StorageClass]] provisioner is named <code>ebs.csi.aws.com</code>.<ref>https://docs.aws.amazon.com/eks/latest/userguide/ebs-csi-migration-faq.html</ref>
 
  
 
== Related ==
 
== Related ==

Revision as of 16:24, 29 February 2024

Amazon EBS CSI driver


Events

kubectl get events
default 8m51s       Warning   FailedScheduling       pod/myprometheus-alertmanager-5967d4ff85-5glkh    running PreBind plugin "VolumeBinding": binding volumes: timed out waiting for the condition
default     4m58s       Normal    ExternalProvisioning   persistentvolumeclaim/myprometheus-alertmanager   waiting for a volume to be created, either by external provisioner "ebs.csi.aws.com" or manually created by system administrator

Related

See also

Advertising: