Closed leveryd closed 1 year ago
第一次在百度云cce集群部署asm实例时,机器资源如下:
在部署asm实例时,有三个pod因为pvc没有绑定,所以处于pending状态,如下
➜ ~ kubectl get pods -n test NAME READY STATUS RESTARTS AGE argo-workflows-app-server-d9b5c846b-pzhw4 0/1 ImagePullBackOff 0 24m argo-workflows-app-workflow-controller-74d9ddd8c5-bq2ns 0/1 ImagePullBackOff 0 24m console-56986fc6ff-r5nqm 3/3 Running 4 (21m ago) 24m crawler-7cd599fd46-zfhn5 2/2 Running 0 24m minio-6c74487844-zqd4d 1/1 Running 0 24m postgres-546d9d68b-9rjjr 0/1 ImagePullBackOff 0 24m release-name-kafka-0 0/1 Pending 0 24m release-name-zookeeper-0 0/1 Pending 0 24m xray-proxy-795f9bf696-9qdp4 1/1 Running 0 24m xray-webhook-6fb5544f8f-9dbzj 1/1 Running 0 24m ➜ ~ kubectl describe pod release-name-zookeeper-0 -n test ... Events: Type Reason Age From Message ---- ------ ---- ---- ------- Warning FailedScheduling 10s (x25 over 25m) default-scheduler 0/2 nodes are available: 2 pod has unbound immediate PersistentVolumeClaims. ➜ ~ kubectl describe pod release-name-kafka-0 -n test ... Events: Type Reason Age From Message ---- ------ ---- ---- ------- Warning FailedScheduling 78s (x26 over 27m) default-scheduler 0/2 nodes are available: 2 pod has unbound immediate PersistentVolumeClaims.
带来的影响:crawler服务无法使用
有两种解决办法:
kubesphere
openebs
kubesphere默认也会安装ingress控制器
第一次在百度云cce集群部署asm实例时,机器资源如下:
在部署asm实例时,有三个pod因为pvc没有绑定,所以处于pending状态,如下
带来的影响:crawler服务无法使用