Difference between revisions of "ExternalProvisioning"
Jump to navigation
Jump to search
Tags: Mobile web edit, Mobile edit |
|||
| Line 2: | Line 2: | ||
| − | 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 |
Revision as of 10:35, 8 March 2023
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
waiting for a volume to be created, either by external provisioner "pd.csi.storage.gke.io" or manually created by system administrator
See also
kubectl get events, OOMKilling, FailedKillPod, SuccessfulDelete, SuccessfulCreate, NoPods, Warning, Critical, NodeSysctlChange, FailedAttachVolume, FailedMount, UnAvailableLoadBalancer, FailedCreatePodSandBox, InvalidDiskCapacity, Scheduled, NetworkNotReady, Evict, Killing, SuccessfulReconcilied, FailedToUpdateEndpointSlices, BackendNotFound, FailedScheduling, ProvisioningFailed- Kubernetes provisioner:
kubernetes.io/gce-pd, kubernetes.io/aws-ebs, pd.csi.storage.gke.io, k8s.io/minikube-hostpath,ExternalProvisioning,kubectl get provisioner, kubectl describe provisioner, kubectl patch provisioner
Advertising:
