kubernetes - 在 Kubernetes 中挂起 PVC 的原因
问题描述
➜ kubectl get pvc -A
NAMESPACE NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE
blog pg-data Pending gp2 211d
metrics grafana-persistent-storage Pending gp2 248d
➜ kubectl get storageclass gp2
NAME PROVISIONER AGE
gp2 (default) kubernetes.io/aws-ebs 248d
➜ kubectl get storageclass gp2 -o yaml
apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
annotations:
kubectl.kubernetes.io/last-applied-configuration: |
{"apiVersion":"storage.k8s.io/v1","kind":"StorageClass","metadata":{"annotations":{"storageclass.kubernetes.io/is-default-class":"true"},"name":"gp2"},"parameters":{"fsType":"ext4","type":"gp2"},"provisioner":"kubernetes.io/aws-ebs","volumeBindingMode":"WaitForFirstConsumer"}
storageclass.kubernetes.io/is-default-class: "true"
creationTimestamp: "2020-01-08T11:17:47Z"
name: gp2
resourceVersion: "169"
selfLink: /apis/storage.k8s.io/v1/storageclasses/gp2
uid: 7f9e91ad-3208-11ea-b35c-0eb3ba733a77
parameters:
fsType: ext4
type: gp2
provisioner: kubernetes.io/aws-ebs
reclaimPolicy: Delete
volumeBindingMode: WaitForFirstConsumer
➜ k describe pvc grafana-persistent-storage -n metrics
Name: grafana-persistent-storage
Namespace: metrics
StorageClass: gp2
Status: Pending
Volume:
Labels: app=grafana
Annotations: <none>
Finalizers: [kubernetes.io/pvc-protection]
Capacity:
Access Modes:
VolumeMode: Filesystem
Mounted By: <none>
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal WaitForFirstConsumer 29s (x31986 over 5d13h) persistentvolume-controller waiting for first consumer to be created before binding
所以没有与 PVC 相关的体积。真正的原因可能是什么?
解决方案
推荐阅读
- mysql - MySql 平均日期差
- amazon-web-services - AWS Forecast 错误提示过滤器 ID 丢失或无效
- javascript - 如何检查字符串是否包含 NodeJS 中子字符串数组中的文本,然后在数组中找到该子字符串的索引?
- angular - 在全屏模式下按下 esc 时,在 typescript 中抛出警告消息
- c - STM32入门——写BSRR
- haskell - 如何编写haskell函数的lambda演算项,例如map?
- .net - 仅在连接到网络时出现 PostgreSQL 连接错误
- python - 将文本文件中的列值放入python中的列表中
- ruby-on-rails - Ruby on Rails - 使用原始参数在失败的控制器操作上重新呈现表单
- android - Why is LocationCallback not firing within CallbackToFutureAdapter?