kubectl get pods -n kubesphere-system
NAME READY STATUS RESTARTS AGE
ks-account-789cd8bbd5-5qf94 0/1 Init:½ 0 35d
ks-account-789cd8bbd5-gxt2w 0/1 Init:½ 0 35d
ks-account-789cd8bbd5-vrdsb 0/1 Init:½ 0 35d
ks-apigateway-5664c4b76f-jms24 0/1 CrashLoopBackOff 9947 35d
ks-apigateway-5664c4b76f-krz4c 0/1 CrashLoopBackOff 9947 35d
ks-apigateway-5664c4b76f-prrmb 0/1 CrashLoopBackOff 9947 35d
ks-apiserver-75f468d48b-qs8vf 1/1 Running 0 35d
ks-apiserver-75f468d48b-s996j 1/1 Running 0 35d
ks-apiserver-75f468d48b-v7pv6 1/1 Running 0 35d
ks-console-78bddc5bfb-2kv49 1/1 Running 0 35d
ks-console-78bddc5bfb-4rpgm 1/1 Running 0 35d
ks-console-78bddc5bfb-xhhzt 1/1 Running 0 35d
ks-controller-manager-d4788677-fh9mr 1/1 Running 0 35d
ks-controller-manager-d4788677-lzhhs 1/1 Running 0 35d
ks-controller-manager-d4788677-rbwl7 1/1 Running 0 35d
ks-installer-75b8d89dff-mkq48 1/1 Running 0 5d7h
openldap-0 0/1 ContainerCreating 0 35d
redis-ha-haproxy-ffb8d889d-4lgbc 1/1 Running 0 35d
redis-ha-haproxy-ffb8d889d-4mjfv 1/1 Running 0 35d
redis-ha-haproxy-ffb8d889d-g7m99 1/1 Running 0 35d
redis-ha-server-0 0/2 Init:0/1 0 35d kubectl logs ks-apigateway-5664c4b76f-krz4c -n kubesphere-system
[DEV NOTICE] Registered directive ‘authenticate’ before ‘jwt’
[DEV NOTICE] Registered directive ‘authentication’ before ‘jwt’
[DEV NOTICE] Registered directive ‘swagger’ before ‘jwt’
Activating privacy features… done.
2020/06/29 14:38:41 [INFO][cache:0xc0001e3090] Started certificate maintenance routine
E0629 14:38:41.268046 1 redis.go:51] unable to reach redis hostEOF
2020/06/29 14:38:41 EOF
kubectl logs redis-ha-server-0 -n kubesphere-system
error: a container name must be specified for pod redis-ha-server-0, choose one of: [redis sentinel] or one of the init containers: [config-init]
kubectl describe pods redis-ha-server-0 -n kubesphere-system
Name: redis-ha-server-0
Namespace: kubesphere-system
Priority: 0
Node: ×××××××××××××××
Start Time: Mon, 25 May 2020 06:42:06 +0000
Labels: app=redis-ha
controller-revision-hash=redis-ha-server-85c4cd57b
release=ks-redis
statefulset.kubernetes.io/pod-name=redis-ha-server-0
Annotations: checksum/init-config: 3536da7869ab409971a5b4fb4f3624e40b5484be59cba5ce0e741d5f28752cf7
Status: Pending
IP:

IPs: <none>
Controlled By: StatefulSet/redis-ha-server
Init Containers:
config-init:
Container ID:

Image: redis:5.0.5-alpine
Image ID:

Port: <none>
Host Port: <none>
Command:
sh
Args:
/readonly-config/init.sh
State: Waiting
Reason: PodInitializing
Ready: False
Restart Count: 0
Environment:
SENTINEL_ID_0: 76570abc73c20d3c0e6c21105777ed9b0898cb75
SENTINEL_ID_1: 0c5b5dae5039679890d11c4d6b6fb66a08625c08
SENTINEL_ID_2: 0b174d8f2a622ce4e7f303c67ce788c35729251d
Mounts:
/data from data (rw)
/readonly-config from config (ro)
/var/run/secrets/kubernetes.io/serviceaccount from redis-ha-token-scdvl (ro)
Containers:
redis:
Container ID:

Image: redis:5.0.5-alpine
Image ID:

Port: 6379/TCP
Host Port: 0/TCP
Command:
redis-server
Args:
/data/conf/redis.conf
State: Waiting
Reason: PodInitializing
Ready: False
Restart Count: 0
Liveness: tcp-socket :6379 delay=15s timeout=1s period=10s #success=1 #failure=3
Environment: <none>
Mounts:
/data from data (rw)
/var/run/secrets/kubernetes.io/serviceaccount from redis-ha-token-scdvl (ro)
sentinel:
Container ID:

Image: redis:5.0.5-alpine
Image ID:

Port: 26379/TCP
Host Port: 0/TCP
Command:
redis-sentinel
Args:
/data/conf/sentinel.conf
State: Waiting
Reason: PodInitializing
Ready: False
Restart Count: 0
Liveness: tcp-socket :26379 delay=15s timeout=1s period=10s #success=1 #failure=3
Environment: <none>
Mounts:
/data from data (rw)
/var/run/secrets/kubernetes.io/serviceaccount from redis-ha-token-scdvl (ro)
Conditions:
Type Status
Initialized False
Ready False
ContainersReady False
PodScheduled True
Volumes:
data:
Type: PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
ClaimName: data-redis-ha-server-0
ReadOnly: false
config:
Type: ConfigMap (a volume populated by a ConfigMap)
Name: redis-ha-configmap
Optional: false
redis-ha-token-scdvl:
Type: Secret (a volume populated by a Secret)
SecretName: redis-ha-token-scdvl
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 FailedMount 12m (x10002 over 35d) kubelet,×××××××××××× Unable to attach or mount volumes: unmounted volumes=[data], unattached volumes=[config data redis-ha-token-scdvl]: timed out waiting for the condition
Warning FailedMount 118s (x33251 over 35d) kubelet, ××××××××(combined from similar events): MountVolume.SetUp failed for volume “pvc-bcbc10af-f585-4c3a-a7ea-5d87dfaf659f” : mount failed: exit status 32
Mounting command: systemd-run
Mounting arguments: –description=Kubernetes transient mount for /var/lib/kubelet/pods/44756143-b7b7-4bff-8397-a2a095721b82/volumes/kubernetes.ionfs/pvc-bcbc10af-f585-4c3a-a7ea-5d87dfaf659f –scope – mount -t nfs -o _netdev ××××××××××××:/ahs020042/××××××××/kubesphere-system-data-redis-ha-server-0-pvc-bcbc10af-f585-4c3a-a7ea-5d87dfaf659f /var/lib/kubelet/pods/44756143-b7b7-4bff-8397-a2a095721b82/volumes/kubernetes.ionfs/pvc-bcbc10af-f585-4c3a-a7ea-5d87dfaf659f
Output: Running scope as unit run-104641.scope.
mount: wrong fs type, bad option, bad superblock on ××××××:/ahs020042/×××××××/kubesphere-system-data-redis-ha-server-0-pvc-bcbc10af-f585-4c3a-a7ea-5d87dfaf659f,
missing codepage or helper program, or other error
(for several filesystems (e.g. nfs, cifs) you might
need a /sbin/mount.<type> helper program)

   In some cases useful info is found in syslog - try
   dmesg | tail or so.

截屏看起来更清晰一些,可能是存储的问题。

看起来 是不是redis 或是 pvc 的有问题