kubectl get pods -n kubesphere-system
NAME READY STATUS RESTARTS AGE
ks-account-789cd8bbd5-5qf94 0/1 Init:½ 0 138m
ks-account-789cd8bbd5-gxt2w 0/1 Init:½ 0 138m
ks-account-789cd8bbd5-vrdsb 0/1 Init:½ 0 138m
ks-apigateway-5664c4b76f-jms24 0/1 CrashLoopBackOff 32 138m
ks-apigateway-5664c4b76f-krz4c 0/1 Error 32 138m
ks-apigateway-5664c4b76f-prrmb 0/1 CrashLoopBackOff 32 138m
ks-apiserver-75f468d48b-qs8vf 1/1 Running 0 138m
ks-apiserver-75f468d48b-s996j 1/1 Running 0 138m
ks-apiserver-75f468d48b-v7pv6 1/1 Running 0 138m
ks-console-78bddc5bfb-2kv49 1/1 Running 0 138m
ks-console-78bddc5bfb-4rpgm 1/1 Running 0 138m
ks-console-78bddc5bfb-xhhzt 1/1 Running 0 138m
ks-controller-manager-d4788677-fh9mr 1/1 Running 0 138m
ks-controller-manager-d4788677-lzhhs 1/1 Running 0 138m
ks-controller-manager-d4788677-rbwl7 1/1 Running 0 138m
ks-installer-75b8d89dff-t9mmf 1/1 Running 0 140m
openldap-0 0/1 ContainerCreating 0 139m
redis-ha-haproxy-ffb8d889d-4lgbc 1/1 Running 0 139m
redis-ha-haproxy-ffb8d889d-4mjfv 1/1 Running 0 139m
redis-ha-haproxy-ffb8d889d-g7m99 1/1 Running 0 139m
redis-ha-server-0 0/2 Init:0/1 0 139m
kubectl describe pods ks-apigateway-5664c4b76f-jms24 -n kubesphere-system
Name: ks-apigateway-5664c4b76f-jms24
Namespace: kubesphere-system
Priority: 0
Node: node-10-120-13-236/10.120.13.236
Start Time: Mon, 25 May 2020 08:42:30 +0200
Labels: app=ks-apigateway
pod-template-hash=5664c4b76f
tier=backend
version=v2.1.1
Annotations: cni.projectcalico.org/podIP: 192.168.100.5/32
Status: Running
IP: 192.168.100.5
IPs:
IP: 192.168.100.5
Controlled By: ReplicaSet/ks-apigateway-5664c4b76f
Containers:
ks-apigateway:
Container ID: docker://2645126c6586248201c5eb29a0fe26703e9181509ff9717ef8b01db5666d4b49
Image: kubesphere/ks-apigateway:v2.1.1
Image ID: docker-pullable://kubesphere/ks-apigateway@sha256:805d1e89aebd391d04bcc0d10fcef2529bad88e0919b5751c043a83fd1781592
Port: 2018/TCP
Host Port: 0/TCP
Command:
/bin/sh
-c
export KUBESPHERE_TOKEN=cat /var/run/secrets/kubernetes.io/serviceaccount/token && ks-apigateway –conf=/etc/caddy/Caddyfile –log=stderr
State: Waiting
Reason: CrashLoopBackOff
Last State: Terminated
Reason: Error
Exit Code: 1
Started: Mon, 25 May 2020 10:56:02 +0200
Finished: Mon, 25 May 2020 10:56:02 +0200
Ready: False
Restart Count: 31
Limits:
cpu: 1
memory: 500Mi
Requests:
cpu: 20m
memory: 100Mi
Environment:
JWT_SECRET: <set to the key ‘jwt-secret’ in secret ‘ks-account-secret’> Optional: false
Mounts:
/etc/caddy from caddyfile (rw)
/etc/kubesphere from kubesphere-config (rw)
/var/run/secrets/kubernetes.io/serviceaccount from kubesphere-token-xxq28 (ro)
Conditions:
Type Status
Initialized True
Ready False
ContainersReady False
PodScheduled True
Volumes:
caddyfile:
Type: ConfigMap (a volume populated by a ConfigMap)
Name: caddyfile
Optional: false
kubesphere-config:
Type: ConfigMap (a volume populated by a ConfigMap)
Name: kubesphere-config
Optional: false
kubesphere-token-xxq28:
Type: Secret (a volume populated by a Secret)
SecretName: kubesphere-token-xxq28
Optional: false
QoS Class: Burstable
Node-Selectors: <none>
Tolerations: CriticalAddonsOnly
node-role.kubernetes.io/master:NoSchedule
node.kubernetes.io/not-ready:NoExecute for 60s
node.kubernetes.io/unreachable:NoExecute for 60s
Events:
Type Reason Age From Message
Warning BackOff 2m51s (x631 over 137m) kubelet, node-10-120-13-236 Back-off restarting failed container
kubectl logs ks-apigateway-5664c4b76f-jms24 -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/05/25 09:01:03 [INFO][cache:0xc000760d70] Started certificate maintenance routine
E0525 09:01:03.253141 1 redis.go:51] unable to reach redis hostEOF
2020/05/25 09:01:03 EOF
