<p>I am using kubernetes(v1.15.2) to manage my skywalking-ui(v6.5.0) apps,recently I found some app's not accessable but the pod is still running, I am not sure the app is works fine,there is no error output in pod's logs.But the pod status icon give tips: <code>the pod is in pending state</code>.</p>

<p><a href="https://i.stack.imgur.com/rmTwu.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/rmTwu.png" alt="enter image description here"></a></p>

<p>Why the status not same in different places?The service is down now.How to avoid this situation or make the service recover automatic? This is pod info:</p>

<pre><code>$ kubectl describe pod ws-red-envelope-service-575dc8f4fb-mg72g
Name:           ws-red-envelope-service-575dc8f4fb-mg72g
Namespace:      dabai-fat
Priority:       0
Node:           azshara-k8s01/172.19.104.231
Start Time:     Sat, 29 Feb 2020 23:07:43 +0800
Labels:         k8s-app=ws-red-envelope-service
                pod-template-hash=575dc8f4fb
Annotations:    &lt;none&gt;
Status:         Running
IP:             172.30.224.4
IPs:            &lt;none&gt;
Controlled By:  ReplicaSet/ws-red-envelope-service-575dc8f4fb
Containers:
  ws-red-envelope-service:
    Container ID:   docker://d1459b7edc1c02f1558b773f89711eeb63c12c9f180a8a426a3dc31d081b2a88
    Image:          registry.cn-hangzhou.aliyuncs.com/dabai_app_k8s/dabai_fat/ws-red-envelope:v0.0.1
    Image ID:       docker-pullable://registry.cn-hangzhou.aliyuncs.com/dabai_app_k8s/dabai_fat/ws-red-envelope@sha256:448c47db9d1366c9e50984054812ebed9cbcc718e206d20600e6c8ac02a35625
    Port:           &lt;none&gt;
    Host Port:      &lt;none&gt;
    State:          Running
      Started:      Sat, 29 Feb 2020 23:07:45 +0800
    Ready:          True
    Restart Count:  0
    Environment:
      APOLLO_META:  &lt;set to the key 'apollo.meta' of config map 'fat-config'&gt;  Optional: false
      ENV:          &lt;set to the key 'env' of config map 'fat-config'&gt;          Optional: false
    Mounts:
      /var/run/secrets/kubernetes.io/serviceaccount from default-token-xnrwt (ro)
Conditions:
  Type              Status
  Initialized       True
  Ready             False
  ContainersReady   True
  PodScheduled      True
Volumes:
  default-token-xnrwt:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  default-token-xnrwt
    Optional:    false
QoS Class:       BestEffort
Node-Selectors:  &lt;none&gt;
Tolerations:     node.kubernetes.io/not-ready:NoExecute for 360s
                 node.kubernetes.io/unreachable:NoExecute for 360s
Events:
  Type    Reason     Age   From                    Message
  ----    ------     ----  ----                    -------
  Normal  Scheduled  12h   default-scheduler       Successfully assigned dabai-fat/ws-red-envelope-service-575dc8f4fb-mg72g to azshara-k8s01
  Normal  Pulled     12h   kubelet, azshara-k8s01  Container image "registry.cn-hangzhou.aliyuncs.com/dabai_app_k8s/dabai_fat/ws-red-envelope:v0.0.1" already present on machine
  Normal  Created    12h   kubelet, azshara-k8s01  Created container ws-red-envelope-service
  Normal  Started    12h   kubelet, azshara-k8s01  Started container ws-red-envelope-service
</code></pre>

Dolphin
<p>So you can see this more clearly in the output. The pod is Running but the Ready flag is false meaning the container is up but is failing the Readiness Probe.</p>
