【疑问】安装milvus集群时,pvc一直是pending状态,找不到sc #41310
Replies: 1 comment 1 reply
-
You need set your storageclass as default storageclass. @mike5MJ |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
背景:最近在部署milvus集群,执行kubectl apply -f milvus_cluster_default.yaml后,pod是pending状态,一路查下来,发下pvc也是pending,也在报错,具体如下。
1.获取PVC状态显示pending,命令kubectl get pvc显示如下
NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE
data-my-release-etcd-0 Pending 64m
data-my-release-etcd-1 Pending 64m
data-my-release-etcd-2 Pending 64m
2.查看pvc日志提示找不到sc,命令kubectl describe pvc data-my-release-etcd-0显示如下
Name: data-my-release-etcd-0
Namespace: default
StorageClass:
Status: Pending
Volume:
Labels: app.kubernetes.io/instance=my-release-etcd
app.kubernetes.io/name=etcd
Annotations:
Finalizers: [kubernetes.io/pvc-protection]
Capacity:
Access Modes:
VolumeMode: Filesystem
Used By: my-release-etcd-0
Events:
Type Reason Age From Message
Normal FailedBinding 4s (x262 over 65m) persistentvolume-controller no persistent volumes available for this claim and no storage class is set
3.查看sc,命令kubectl get sc显示如下
NAME PROVISIONER RECLAIMPOLICY VOLUMEBINDINGMODE ALLOWVOLUMEEXPANSION AGE
managed-nfs-storage fuseim.pri/ifs Delete Immediate false 20h
4.部署参考的官方文档https://milvus.io/docs/zh/install_cluster-milvusoperator.md,首页-文档-开始-安装 Milvus-运行 Milvus Distributed-Milvus Operator-使用 Milvus Operator 在 Kubernetes 中运行 Milvus
5.milvus_cluster_default.yaml文件使用的是https://github.com/zilliztech/milvus-operator/blob/main/config/samples/cluster_demo.yaml
Beta Was this translation helpful? Give feedback.
All reactions