Kubernetes，活力探测失败但是pod处于Running状态

我正在尝试用kubernetes进行部署，我已经按照它，https： //www.ianlewis.org/en/bluegreen-deployments-kubernetes，没关系。我添加了一个活动探针来执行健康检查，

apiVersion: extensions/v1beta1
kind: Deployment
metadata:
name: flask-1.3
spec:
replicas: 2
template:

metadata:
  labels:
    name: app
    version: "1.3"
spec:
  containers: 
    - name: appflask
      image: 192.168.99.100:5000/fapp:1.2
      livenessProbe:
        httpGet:
         path: /index2
         port: 5000
        failureThreshold: 1
        periodSeconds: 1
        initialDelaySeconds: 1
      ports:
        - name: http
          containerPort: 5000

路径“index2”不存在，我想测试失败的部署。问题是我执行时：

kubectl get pods -o wide
几秒钟之一其中一个pods状态为“RUNNING”

NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES

flask-1.3-6c644b8648-878qz 0/1 CrashLoopBackOff 6 6m19s 10.244.1.250 node
flask-1.3-6c644b8648-t6qhv 0/1 CrashLoopBackOff 7 6m19s 10.244.2.230 nod2e
几秒钟后，一个pod正在RUNNING，当live失败时：

NAME READY STATUS RESTARTS AGE

IP             NODE    NOMINATED NODE   READINESS GATES

flask-1.3-6c644b8648-878qz 1/1 Running 7 6m20s 10.244.1.250 node

flask-1.3-6c644b8648-t6qhv   0/1     CrashLoopBackOff   7          6m20s   10.244.2.230   nod2e   <none>           <none>

在运行回到CrashLoopBackOff之后，问题是，为什么如果livenesprobe总是失败，它会在几秒钟内保持运行？