感谢那么快的答复。
当前状态是这样的：
Name: openldap-0
Namespace: kubesphere-system
Priority: 0
Node: cn-shanghai.192.168.1.143/192.168.1.143
Start Time: Fri, 27 Nov 2020 10:51:39 +0800
Labels: app.kubernetes.io/instance=ks-openldap
app.kubernetes.io/name=openldap-ha
controller-revision-hash=openldap-5d5b768f7b
statefulset.kubernetes.io/pod-name=openldap-0
Annotations: kubernetes.io/psp: ack.privileged
Status: Running
IP: 172.20.0.205
IPs:
IP: 172.20.0.205
Controlled By: StatefulSet/openldap
Containers:
openldap-ha:
Container ID: docker://d86bb9496f6aa7673677cbb1aae7b30222593042b0603552524eec37199958f7
Image: osixia/openldap:1.3.0
Image ID: docker-pullable://osixia/openldap@sha256:66bf8dafc3c47a387dfa9d87425acab96acd8a3f2a62a8f6393584c27777cb41
Port: 389/TCP
Host Port: 0/TCP
Command:
/bin/sh
-ce
tail -f /dev/null
State: Running
Started: Fri, 27 Nov 2020 10:51:40 +0800
Ready: False
Restart Count: 0
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_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 volume-openldap-pvc-openldap-0 (rw)
/var/lib/ldap from volume-openldap-pvc-openldap-0 (rw)
/var/run/secrets/kubernetes.io/serviceaccount from default-token-94w4w (ro)
Conditions:
Type Status
Initialized True
Ready False
ContainersReady False
PodScheduled True
Volumes:
openldap-pvc:
Type: PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
ClaimName: openldap-pvc-openldap-0
ReadOnly: false
volume-openldap-pvc-openldap-0:
Type: PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
ClaimName: openldap-pvc-openldap-0
ReadOnly: false
default-token-94w4w:
Type: Secret (a volume populated by a Secret)
SecretName: default-token-94w4w
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
Normal Scheduled <unknown> default-scheduler Successfully assigned kubesphere-system/openldap-0 to cn-shanghai.192.168.1.143
Normal Pulled 51s kubelet, cn-shanghai.192.168.1.143 Container image “osixia/openldap:1.3.0” already present on machine
Normal Created 51s kubelet, cn-shanghai.192.168.1.143 Created container openldap-ha
Normal Started 51s kubelet, cn-shanghai.192.168.1.143 Started container openldap-ha
Warning Unhealthy 5s (x2 over 20s) kubelet, cn-shanghai.192.168.1.143 Liveness probe failed: dial tcp 172.20.0.205:389: connect: connection refused
Warning Unhealthy 4s (x2 over 19s) kubelet, cn-shanghai.192.168.1.143 Readiness probe failed: dial tcp 172.20.0.205:389: connect: connection refused
[root@elec-iot002 ~]#
[root@elec-iot002 ~]#
