Jeff 检查后是存储卷绑定失败了，这种情况怎么处理啊，新手小白，见谅。。
[root@master ]# kubectl describe pod openldap-0 -n kubesphere-system
Name: openldap-0
Namespace: kubesphere-system
Priority: 0
Node: <none>
Labels: app.kubernetes.io/instance=ks-openldap
app.kubernetes.io/name=openldap-ha
controller-revision-hash=openldap-5b89576789
statefulset.kubernetes.io/pod-name=openldap-0
Annotations: <none>
Status: Pending
IP:
IPs: <none>
Controlled By: StatefulSet/openldap
Containers:
openldap-ha:
Image: osixia/openldap:1.3.0
Port: 389/TCP
Host Port: 0/TCP
Args:
–copy-service
–loglevel=warning
Liveness: tcp-socket :389 delay=30s timeout=1s period=15s #success=1 #failure=3
Readiness: tcp-socket :389 delay=30s timeout=1s period=15s #success=1 #failure=3
Environment:
LDAP_ORGANISATION: kubesphere
LDAP_DOMAIN: kubesphere.io
LDAP_CONFIG_PASSWORD: admin
LDAP_ADMIN_PASSWORD: admin
LDAP_REPLICATION: false
LDAP_TLS: false
LDAP_REMOVE_CONFIG_AFTER_SETUP: true
MY_POD_NAME: openldap-0 (v1:metadata.name)
HOSTNAME: $(MY_POD_NAME).openldap
Mounts:
/etc/ldap/slapd.d from openldap-pvc (rw,path=“ldap-config”)
/var/lib/ldap from openldap-pvc (rw,path=“ldap-data”)
/var/run/secrets/kubernetes.io/serviceaccount from default-token-96d75 (ro)
Conditions:
Type Status
PodScheduled False
Volumes:
openldap-pvc:
Type: PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
ClaimName: openldap-pvc-openldap-0
ReadOnly: false
default-token-96d75:
Type: Secret (a volume populated by a Secret)
SecretName: default-token-96d75
Optional: false
QoS Class: BestEffort
Node-Selectors: <none>
Tolerations: CriticalAddonsOnly
node-role.kubernetes.io/master:NoSchedule
node.kubernetes.io/not-ready:NoExecute for 300s
node.kubernetes.io/unreachable:NoExecute for 300s
Events:
Type Reason Age From Message
Warning FailedScheduling 6m3s (x11 over 107m) default-scheduler Failed to bind volumes: timed out waiting for the condition
