部署出现 pod has unbound immediate PersistentVolumeClaims. 问题

【 TiDB 使用环境】生产环境 /测试/ Poc
【 TiDB 版本】
【复现路径】做过哪些操作出现的问题
【遇到的问题:问题现象及影响】
Events:
Type Reason Age From Message


Warning FailedScheduling 3m34s (x3 over 13m) default-scheduler 0/3 nodes are available: pod has unbound immediate PersistentVolumeClaims. preemption: 0/3 nodes are available: 3 Preemption is not helpful for scheduling.

【资源配置】进入到 TiDB Dashboard -集群信息 (Cluster Info) -主机(Hosts) 截图此页面
【附件:截图/日志/监控】
k8s v1.31.3
tidb-operator:v1.6.0

Warning FailedScheduling 60s (x8 over 36m) default-scheduler 0/3 nodes are available: pod has unbound immediate PersistentVolumeClaims. preemption: 0/3 nodes are available: 3 Preemption is not helpful for scheduling.


公有云的云盘用 WaitForFirstConsumer
https://docs.pingcap.com/zh/tidb-in-kubernetes/stable/deploy-on-aws-eks#gp3-存储类型推荐或其他-ebs-存储类型

私有云本地盘根据环境策略用 Immediate
https://docs.pingcap.com/zh/tidb-in-kubernetes/stable/configure-storage-class#数据安全

1 个赞