一起来学k8s 05.health check

最新推荐文章于 2024-06-17 10:57:22 发布
最新推荐文章于 2024-06-17 10:57:22 发布
阅读量1.8k 收藏 1
点赞数
分类专栏： kubernetes 文章标签： kubernetes
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/tangwei0928/article/details/94408815
版权

Pod Health Check

在Kubernetes集群当中，我们可以通过配置liveness probe（存活探针）和readiness probe（可读性探针）来影响容器的生存周期。

  1. 使用 liveness probe 来确定你的应用程序是否正在运行，通俗点将就是是否还活着。一般来说，如果你的程序一旦崩溃了， Kubernetes 就会立刻知道这个程序已经终止了，然后就会重启这个程序。而我们的 liveness probe 的目的就是来捕获到当前应用程序还没有终止，还没有崩溃，如果出现了这些情况，那么就重启处于该状态下的容器，使应用程序在存在 bug 的情况下依然能够继续运行下去。
  2. 使用 readiness probe 来确定容器是否已经就绪可以接收流量过来了。这个探针通俗点讲就是说是否准备好了，现在可以开始工作了。只有当 Pod 中的容器都处于就绪状态的时候 kubelet 才会认定该 Pod 处于就绪状态，因为一个 Pod 下面可能会有多个容器。当然 Pod 如果处于非就绪状态，那么我们就会将他从我们的工作队列中移除出来，这样我们的流量就不会被路由到这个 Pod 里面来了。

这两个探针的支持两种配置方式：

exec：执行一段命令
http：检测某个http请求
tcpSocket：检查端口

环境

192.168.48.101 master01
192.168.48.201 node01
192.168.48.202 node02

liveness probe

准备模板health-hook.yaml

vim health-pod.yaml

apiVersion: v1
kind: Pod
metadata:
  name: health-pod
  namespace: default
  labels:
    app: myapp
    type: pod
spec:
  containers:
  - name: myapp
    image: ikubernetes/myapp:v1
    ports:
    - name: http
      containerPort: 80
  - name: busybox
    image: busybox:latest
    command:
    - "/bin/sh"
    - "-c"
    - "mkdir -p /usr/share/nginx/html; echo $(date) >> /usr/share/nginx/html/test.html;sleep 3600"

exec

编写exec-health-hook.yaml

cp health-hook.yaml  exec-health-hook.yaml 
vim exec-health-hook.yaml 

apiVersion: v1
kind: Pod
metadata:
  name: exec-health-pod
  namespace: default
  labels:
    app: myapp
    type: pod
spec:
  containers:
  - name: myapp
    image: ikubernetes/myapp:v1
    ports:
    - name: http
      containerPort: 80
  - name: busybox
    image: busybox:latest
    command:
    - "/bin/sh"
    - "-c"
    - "touch /tmp/health; sleep 30; rm -rf /tmp/healthy; sleep 600"
    livenessProbe:
      exec:
        command: ["cat /tmp/health"]
      initialDelaySeconds: 5
      periodSeconds: 5

创建exec-health-hook.yaml

[root@master01 pod_yaml]# kubectl apply -f exec-health-hook.yaml 
pod/exec-health-pod created

[root@master01 pod_yaml]# kubectl get pod
NAME                 READY   STATUS    RESTARTS   AGE
demo-pod             2/2     Running   14         6d5h
demo-pod-ssd         1/1     Running   2          4d21h
exec-health-pod      2/2     Running   0          86s
poststart-hook-pod   2/2     Running   1          86m


initialDelaySeconds：第一次执行探针的时候要等待时间
periodSeconds:每隔多久执行一次存活探针

设置initialDelaySeconds表示在第一次执行探针的时候要等待5秒，这样能够确保我们的容器能够有足够的时间启动起来。设置periodSeconds属性表示让kubelet每隔5秒执行一次存活探针，也就是每5秒执行一次上面的cat /tmp/healthy命令，如果命令执行成功了，将返回0，那么kubelet就会认为当前这个容器是存活的并且很监控，如果返回的是非0值，那么kubelet就会把该容器杀掉然后重启它。

探针还可以配置如下几个参数
timeoutSeconds：探测超时时间，默认1秒，最小1秒。
successThreshold：探测失败后，最少连续探测成功多少次才被认定为成功。默认是 1，但是如果是`liveness`则必须是 1，最小值是 1。
failureThreshold：探测成功后，最少连续探测失败多少次才被认定为失败。默认是 3，最小值是 1。

观察是否重启

[root@master01 pod_yaml]# kubectl get pod -w
NAME                 READY   STATUS    RESTARTS   AGE
demo-pod             2/2     Running   14         6d5h
demo-pod-ssd         1/1     Running   2          4d21h
exec-health-pod      2/2     Running   0          94s
poststart-hook-pod   2/2     Running   1          86m
exec-health-pod      2/2     Running   1          2m33s

http

编写http-health-hook.yaml

cp health-hook.yaml http-health-hook.yaml 
vim http-health-hook.yaml 

apiVersion: v1
kind: Pod
metadata:
  name: http-health-pod
  namespace: default
  labels:
    app: myapp
    type: pod
spec:
  containers:
  - name: myapp
    image: ikubernetes/myapp:v1
    ports:
    - name: http
      containerPort: 80
    livenessProbe:
      httpGet:
        path: /index.html
        port: 80
      initialDelaySeconds: 3
      periodSeconds: 3
  - name: busybox
    image: busybox:latest
    command:
    - "/bin/sh"
    - "-c"
    - "mkdir -p /usr/share/nginx/html; echo $(date) >> /usr/share/nginx/html/test.html;sleep 3600"

创建http-health-hook.yaml

[root@master01 pod_yaml]# kubectl apply -f http-health-hook.yaml 
pod/http-health-pod created
[root@master01 pod_yaml]# kubectl get pod -o wide
NAME                 READY   STATUS    RESTARTS   AGE     IP           NODE     NOMINATED NODE   READINESS GATES
demo-pod             2/2     Running   15         6d6h    10.244.2.7   node02   <none>           <none>
demo-pod-ssd         1/1     Running   2          4d22h   10.244.1.7   node01   <none>           <none>
http-health-pod      2/2     Running   0          3m25s   10.244.2.9   node02   <none>           <none>
poststart-hook-pod   2/2     Running   2          148m    10.244.1.8   node01   <none>           <none>
[root@master01 pod_yaml]# curl 10.244.2.9
Hello MyApp | Version: v1 | <a href="hostname.html">Pod Name</a>

手动删除index.html文件 观察是否重启

[root@master01 pod_yaml]# kubectl exec http-health-pod -c myapp -it -- /bin/sh
/ # cd /usr/share/nginx/html/
/usr/share/nginx/html # rm -rf index.html 
/usr/share/nginx/html # command terminated with exit code 137
[root@master01 pod_yaml]# 
[root@master01 pod_yaml]# kubectl get pod -o wide
NAME                 READY   STATUS    RESTARTS   AGE     IP           NODE     NOMINATED NODE   READINESS GATES
demo-pod             2/2     Running   15         6d6h    10.244.2.7   node02   <none>           <none>
demo-pod-ssd         1/1     Running   2          4d22h   10.244.1.7   node01   <none>           <none>
http-health-pod      2/2     Running   1          6m57s   10.244.2.9   node02   <none>           <none>
poststart-hook-pod   2/2     Running   2          151m    10.244.1.8   node01   <none>           <none>

tcpSocket

编写tcpsocket-health-hook.yaml

cp health-hook.yaml tcpsocket-health-hook.yaml 
vim tcpsocket-health-hook.yaml 

apiVersion: v1
kind: Pod
metadata:
  name: tcpsocket-health-pod
  namespace: default
  labels:
    app: myapp
    type: pod
spec:
  containers:
  - name: myapp
    image: ikubernetes/myapp:v1
    ports:
    - name: http
      containerPort: 80
    livenessProbe:
      tcpSocket:
        port: 80
      initialDelaySeconds: 15
      periodSeconds: 20
  - name: busybox
    image: busybox:latest
    command:
    - "/bin/sh"
    - "-c"
    - "mkdir -p /usr/share/nginx/html; echo $(date) >> /usr/share/nginx/html/test.html;sleep 3600"

创建tcpsocket-health-hook.yaml

[root@master01 pod_yaml]# kubectl apply -f tcpsocket-health-hook.yaml 
pod/tcpsocket-health-pod created
[root@master01 pod_yaml]# kubectl get pod -o wide
NAME                   READY   STATUS    RESTARTS   AGE     IP            NODE     NOMINATED NODE   READINESS GATES
demo-pod               2/2     Running   15         6d6h    10.244.2.7    node02   <none>           <none>
demo-pod-ssd           1/1     Running   2          4d22h   10.244.1.7    node01   <none>           <none>
http-health-pod        2/2     Running   1          14m     10.244.2.9    node02   <none>           <none>
poststart-hook-pod     2/2     Running   2          159m    10.244.1.8    node01   <none>           <none>
tcpsocket-health-pod   2/2     Running   0          25s     10.244.1.10   node01   <none>           <none>

手动关掉nginx，查看是否重启

[root@master01 pod_yaml]# kubectl exec tcpsocket-health-pod -c myapp -it -- /bin/sh
/ # nginx -s stop
2019/04/06 11:25:42 [notice] 12#12: signal process started
/ # command terminated with exit code 137
[root@master01 pod_yaml]# kubectl get pod -o wide
NAME                   READY   STATUS    RESTARTS   AGE     IP            NODE     NOMINATED NODE   READINESS GATES
demo-pod               2/2     Running   15         6d6h    10.244.2.7    node02   <none>           <none>
demo-pod-ssd           1/1     Running   2          4d22h   10.244.1.7    node01   <none>           <none>
http-health-pod        2/2     Running   1          16m     10.244.2.9    node02   <none>           <none>
poststart-hook-pod     2/2     Running   2          160m    10.244.1.8    node01   <none>           <none>
tcpsocket-health-pod   2/2     Running   1          106s    10.244.1.10   node01   <none>           <none>

readiness probe

exec

编写exec-ready-hook.yaml

cp exec-health-hook.yaml exec-ready-hook.yaml 
vim exec-ready-hook.yaml 

apiVersion: v1
kind: Pod
metadata:
  name: exec-ready-pod
  namespace: default
  labels:
    app: myapp
    type: pod
spec:
  containers:
  - name: myapp
    image: ikubernetes/myapp:v1
    ports:
    - name: http
      containerPort: 80
  - name: busybox
    image: busybox:latest
    command:
    - "/bin/sh"
    - "-c"
    - "touch /tmp/health; sleep 30; rm -rf /tmp/healthy; sleep 600"
    readinessProbe:
      exec:
        command: ["cat /tmp/health"]
      initialDelaySeconds: 5
      periodSeconds: 5

创建exec-ready-hook.yaml

[root@master01 pod_yaml]# kubectl apply -f exec-ready-hook.yaml 
pod/exec-health-pod created
[root@master01 pod_yaml]# kubectl get pod -o wide
NAME                   READY   STATUS    RESTARTS   AGE     IP            NODE     NOMINATED NODE   READINESS GATES
demo-pod               2/2     Running   16         6d6h    10.244.2.7    node02   <none>           <none>
demo-pod-ssd           1/1     Running   2          4d22h   10.244.1.7    node01   <none>           <none>
exec-health-pod        1/2     Running   0          3m30s   10.244.2.10   node02   <none>           <none>
exec-ready-pod         2/2     Running   0          47s     10.244.1.11   node01   <none>           <none>
http-health-pod        2/2     Running   1          27m     10.244.2.9    node02   <none>           <none>
poststart-hook-pod     2/2     Running   2          172m    10.244.1.8    node01   <none>           <none>
tcpsocket-health-pod   2/2     Running   1          13m     10.244.1.10   node01   <none>           <none>

查看pod是否就绪

[root@master01 pod_yaml]# kubectl get pod -o wide -w
NAME                   READY   STATUS    RESTARTS   AGE     IP            NODE     NOMINATED NODE   READINESS GATES
demo-pod               2/2     Running   16         6d6h    10.244.2.7    node02   <none>           <none>
demo-pod-ssd           1/1     Running   2          4d22h   10.244.1.7    node01   <none>           <none>
exec-health-pod        1/2     Running   0          3m30s   10.244.2.10   node02   <none>           <none>
exec-ready-pod         1/2     Running   0          47s     10.244.1.11   node01   <none>           <none>
http-health-pod        2/2     Running   1          27m     10.244.2.9    node02   <none>           <none>
poststart-hook-pod     2/2     Running   2          172m    10.244.1.8    node01   <none>           <none>
tcpsocket-health-pod   2/2     Running   1          13m     10.244.1.10   node01   <none>           <none>

[root@master01 pod_yaml]# kubectl describe pod exec-ready-pod 
Name:               exec-ready-pod
Namespace:          default
Priority:           0
PriorityClassName:  <none>
Node:               node01/192.168.48.201
Start Time:         Sat, 06 Apr 2019 19:36:39 +0800
Labels:             app=myapp
                    type=pod
Annotations:        cni.projectcalico.org/podIP: 10.244.1.11/32
                    kubectl.kubernetes.io/last-applied-configuration:
                      {"apiVersion":"v1","kind":"Pod","metadata":{"annotations":{},"labels":{"app":"myapp","type":"pod"},"name":"exec-ready-pod","namespace":"de...
Status:             Running
IP:                 10.244.1.11
Containers:
  myapp:
    Container ID:   docker://1eff9a86d080d66b97444326053bac735f9914c53bff2a42db9eb5d392294b4d
    Image:          ikubernetes/myapp:v1
    Image ID:       docker-pullable://ikubernetes/myapp@sha256:9c3dc30b5219788b2b8a4b065f548b922a34479577befb54b03330999d30d513
    Port:           80/TCP
    Host Port:      0/TCP
    State:          Running
      Started:      Sat, 06 Apr 2019 19:36:40 +0800
    Ready:          True
    Restart Count:  0
    Environment:    <none>
    Mounts:
      /var/run/secrets/kubernetes.io/serviceaccount from default-token-f9699 (ro)
  busybox:
    Container ID:  docker://b411a4285635a04810a138d6029025273299023470c45b8ca7f42ddd04a8f0a4
    Image:         busybox:latest
    Image ID:      docker-pullable://busybox@sha256:954e1f01e80ce09d0887ff6ea10b13a812cb01932a0781d6b0cc23f743a874fd
    Port:          <none>
    Host Port:     <none>
    Command:
      /bin/sh
      -c
      touch /tmp/health; sleep 30; rm -rf /tmp/healthy; sleep 600
    State:          Running
      Started:      Sat, 06 Apr 2019 19:37:05 +0800
    Ready:          False
    Restart Count:  0
    Readiness:      exec [cat /tmp/health] delay=5s timeout=1s period=5s #success=1 #failure=3
    Environment:    <none>
    Mounts:
      /var/run/secrets/kubernetes.io/serviceaccount from default-token-f9699 (ro)
Conditions:
  Type              Status
  Initialized       True 
  Ready             False 
  ContainersReady   False 
  PodScheduled      True 
Volumes:
  default-token-f9699:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  default-token-f9699
    Optional:    false
QoS Class:       BestEffort
Node-Selectors:  <none>
Tolerations:     node.kubernetes.io/not-ready:NoExecute for 300s
                 node.kubernetes.io/unreachable:NoExecute for 300s
Events:
  Type     Reason     Age                   From               Message
  ----     ------     ----                  ----               -------
  Normal   Scheduled  3m11s                 default-scheduler  Successfully assigned default/exec-ready-pod to node01
  Normal   Pulled     3m10s                 kubelet, node01    Container image "ikubernetes/myapp:v1" already present on machine
  Normal   Created    3m10s                 kubelet, node01    Created container myapp
  Normal   Started    3m10s                 kubelet, node01    Started container myapp
  Normal   Pulling    3m10s                 kubelet, node01    Pulling image "busybox:latest"
  Normal   Pulled     2m45s                 kubelet, node01    Successfully pulled image "busybox:latest"
  Normal   Created    2m45s                 kubelet, node01    Created container busybox
  Normal   Started    2m45s                 kubelet, node01    Started container busybox
  Warning  Unhealthy  71s (x18 over 2m36s)  kubelet, node01    Readiness probe failed: OCI runtime exec failed: exec failed: container_linux.go:345: starting container process caused "exec: \"cat /tmp/health\": stat cat /tmp/health: no such file or directory": unknown

http

编写http-ready-hook.yaml

cp http-health-hook.yaml http-ready-hook.yaml 
vim http-ready-hook.yaml 

apiVersion: v1
kind: Pod
metadata:
  name: http-ready-pod
  namespace: default
  labels:
    app: myapp
    type: pod
spec:
  containers:
  - name: myapp
    image: ikubernetes/myapp:v1
    ports:
    - name: http
      containerPort: 80
    readinessProbe:
      httpGet:
        path: /index.html
        port: 80
      initialDelaySeconds: 3
      periodSeconds: 3
  - name: busybox
    image: busybox:latest
    command:
    - "/bin/sh"
    - "-c"
    - "mkdir -p /usr/share/nginx/html; echo $(date) >> /usr/share/nginx/html/test.html;sleep 3600"

创建http-ready-hook.yaml

[root@master01 pod_yaml]# kubectl apply -f http-ready-hook.yaml 
pod/http-ready-pod created
[root@master01 pod_yaml]# kubectl get pod
NAME                   READY   STATUS    RESTARTS   AGE
demo-pod               2/2     Running   16         6d7h
demo-pod-ssd           1/1     Running   2          4d23h
exec-ready-pod         1/2     Running   2          23m
http-health-pod        2/2     Running   1          50m
http-ready-pod         2/2     Running   0          2m32s
poststart-hook-pod     2/2     Running   3          3h15m
tcpsocket-health-pod   2/2     Running   1          36m

手动删除index.html文件，查看pod是否就绪

[root@master01 pod_yaml]# kubectl exec http-ready-pod -c myapp -it -- /bin/sh
/ # cd /usr/share/nginx/html/
/usr/share/nginx/html # rm -rf index.html 
/usr/share/nginx/html # 
[root@master01 pod_yaml]# kubectl get pod -o wide
NAME                   READY   STATUS    RESTARTS   AGE     IP            NODE     NOMINATED NODE   READINESS GATES
demo-pod               2/2     Running   16         6d7h    10.244.2.7    node02   <none>           <none>
demo-pod-ssd           1/1     Running   2          4d23h   10.244.1.7    node01   <none>           <none>
exec-ready-pod         1/2     Running   2          26m     10.244.1.11   node01   <none>           <none>
http-health-pod        2/2     Running   1          52m     10.244.2.9    node02   <none>           <none>
http-ready-pod         1/2     Running   0          4m58s   10.244.2.11   node02   <none>           <none>
poststart-hook-pod     2/2     Running   3          3h17m   10.244.1.8    node01   <none>           <none>
tcpsocket-health-pod   2/2     Running   1          38m     10.244.1.10   node01   <none>           <none>
[root@master01 pod_yaml]# kubectl describe pod http-ready-pod 
Name:               http-ready-pod
Namespace:          default
Priority:           0
PriorityClassName:  <none>
Node:               node02/192.168.48.202
Start Time:         Sat, 06 Apr 2019 19:57:42 +0800
Labels:             app=myapp
                    type=pod
Annotations:        cni.projectcalico.org/podIP: 10.244.2.11/32
                    kubectl.kubernetes.io/last-applied-configuration:
                      {"apiVersion":"v1","kind":"Pod","metadata":{"annotations":{},"labels":{"app":"myapp","type":"pod"},"name":"http-ready-pod","namespace":"de...
Status:             Running
IP:                 10.244.2.11
Containers:
  myapp:
    Container ID:   docker://365be76d72546b736b2e119acda1b315d5c4fa498d4e7769d49421c8639b5d01
    Image:          ikubernetes/myapp:v1
    Image ID:       docker-pullable://ikubernetes/myapp@sha256:9c3dc30b5219788b2b8a4b065f548b922a34479577befb54b03330999d30d513
    Port:           80/TCP
    Host Port:      0/TCP
    State:          Running
      Started:      Sat, 06 Apr 2019 19:57:43 +0800
    Ready:          False
    Restart Count:  0
    Readiness:      http-get http://:80/index.html delay=3s timeout=1s period=3s #success=1 #failure=3
    Environment:    <none>
    Mounts:
      /var/run/secrets/kubernetes.io/serviceaccount from default-token-f9699 (ro)
  busybox:
    Container ID:  docker://270ab33e2e6ab299e6f5dd3fc4641a72e97004a249b599e47af981dcde172cda
    Image:         busybox:latest
    Image ID:      docker-pullable://busybox@sha256:954e1f01e80ce09d0887ff6ea10b13a812cb01932a0781d6b0cc23f743a874fd
    Port:          <none>
    Host Port:     <none>
    Command:
      /bin/sh
      -c
      mkdir -p /usr/share/nginx/html; echo $(date) >> /usr/share/nginx/html/test.html;sleep 3600
    State:          Running
      Started:      Sat, 06 Apr 2019 19:58:13 +0800
    Ready:          True
    Restart Count:  0
    Environment:    <none>
    Mounts:
      /var/run/secrets/kubernetes.io/serviceaccount from default-token-f9699 (ro)
Conditions:
  Type              Status
  Initialized       True 
  Ready             False 
  ContainersReady   False 
  PodScheduled      True 
Volumes:
  default-token-f9699:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  default-token-f9699
    Optional:    false
QoS Class:       BestEffort
Node-Selectors:  <none>
Tolerations:     node.kubernetes.io/not-ready:NoExecute for 300s
                 node.kubernetes.io/unreachable:NoExecute for 300s
Events:
  Type     Reason     Age                 From               Message
  ----     ------     ----                ----               -------
  Normal   Scheduled  5m38s               default-scheduler  Successfully assigned default/http-ready-pod to node02
  Normal   Pulled     5m38s               kubelet, node02    Container image "ikubernetes/myapp:v1" already present on machine
  Normal   Created    5m38s               kubelet, node02    Created container myapp
  Normal   Started    5m38s               kubelet, node02    Started container myapp
  Normal   Pulling    5m38s               kubelet, node02    Pulling image "busybox:latest"
  Normal   Pulled     5m8s                kubelet, node02    Successfully pulled image "busybox:latest"
  Normal   Created    5m8s                kubelet, node02    Created container busybox
  Normal   Started    5m8s                kubelet, node02    Started container busybox
  Warning  Unhealthy  23s (x19 over 77s)  kubelet, node02    Readiness probe failed: HTTP probe failed with statuscode: 404

tcpsocket

编写tcpsocket-ready-hook.yaml

cp tcpsocket-health-hook.yaml tcpsocket-ready-hook.yaml 
vim tcpsocket-ready-hook.yaml 

apiVersion: v1
kind: Pod
metadata:
  name: tcpsocket-ready-pod
  namespace: default
  labels:
    app: myapp
    type: pod
spec:
  containers:
  - name: myapp
    image: ikubernetes/myapp:v1
    ports:
    - name: http
      containerPort: 80
    readinessProbe:
      tcpSocket:
        port: 80
      initialDelaySeconds: 15
      periodSeconds: 20
  - name: busybox
    image: busybox:latest
    command:
    - "/bin/sh"
    - "-c"
    - "mkdir -p /usr/share/nginx/html; echo $(date) >> /usr/share/nginx/html/test.html;sleep 3600"

创建tcpsocket-ready-hook.yaml

[root@master01 pod_yaml]# kubectl apply -f tcpsocket-ready-hook.yaml 
pod/tcpsocket-ready-pod created
[root@master01 pod_yaml]# kubectl get pod  -o wide
NAME                           READY   STATUS    RESTARTS   AGE     IP           NODE     NOMINATED NODE   READINESS GATES
demo-deploy-8675c97685-vhncn   1/1     Running   0          6d8h    10.244.2.5   node02   <none>           <none>
demo-deploy-8675c97685-w7md2   1/1     Running   0          6d8h    10.244.1.5   node01   <none>           <none>
demo-pod                       2/2     Running   2          6d8h    10.244.2.4   node02   <none>           <none>
tcpsocket-ready-pod            2/2     Running   0          8m47s   10.244.1.6   node01   <none>           <none>

手动改80端口，改成89，再看看是否就绪

[root@master01 pod_yaml]# kubectl exec tcpsocket-ready-pod -it -c myapp -- /bin/sh
~ # cd /etc/nginx/
/etc/nginx # cd conf.d/
/etc/nginx/conf.d # vi default.conf 
/etc/nginx/conf.d # nginx -s reload
2019/04/06 13:17:17 [notice] 19#19: signal process started
/etc/nginx/conf.d # netstat -ntlp
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name    
tcp        0      0 0.0.0.0:89              0.0.0.0:*               LISTEN      1/nginx: master pro

[root@master01 pod_yaml]# kubectl get pod -o wide
NAME                           READY   STATUS    RESTARTS   AGE    IP           NODE     NOMINATED NODE   READINESS GATES
demo-deploy-8675c97685-vhncn   1/1     Running   0          6d8h   10.244.2.5   node02   <none>           <none>
demo-deploy-8675c97685-w7md2   1/1     Running   0          6d8h   10.244.1.5   node01   <none>           <none>
demo-pod                       1/2     Running   2          6d8h   10.244.2.4   node02   <none>           <none>
tcpsocket-ready-pod            1/2     Running   0          16m    10.244.1.6   node01   <none>           <none>

[root@master01 pod_yaml]# kubectl describe pod tcpsocket-ready-pod 
Name:               tcpsocket-ready-pod
Namespace:          default
Priority:           0
PriorityClassName:  <none>
Node:               node01/192.168.48.201
Start Time:         Sat, 06 Apr 2019 21:04:50 +0800
Labels:             app=myapp
                    type=pod
Annotations:        kubectl.kubernetes.io/last-applied-configuration:
                      {"apiVersion":"v1","kind":"Pod","metadata":{"annotations":{},"labels":{"app":"myapp","type":"pod"},"name":"tcpsocket-ready-pod","namespace...
Status:             Running
IP:                 10.244.1.6
Containers:
  myapp:
    Container ID:   docker://882eb554046e9f7158edb993eba6d8571af8e87ffed697a4b57afc836ad48015
    Image:          ikubernetes/myapp:v1
    Image ID:       docker-pullable://ikubernetes/myapp@sha256:9c3dc30b5219788b2b8a4b065f548b922a34479577befb54b03330999d30d513
    Port:           80/TCP
    Host Port:      0/TCP
    State:          Running
      Started:      Sat, 06 Apr 2019 21:04:51 +0800
    Ready:          False
    Restart Count:  0
    Readiness:      tcp-socket :80 delay=15s timeout=1s period=20s #success=1 #failure=3
    Environment:    <none>
    Mounts:
      /var/run/secrets/kubernetes.io/serviceaccount from default-token-f9699 (ro)
  busybox:
    Container ID:  docker://dbff1eb869afd6c15e205d6c8d8316eeb3126a82fbb2217a0fa9ce11a1bde06e
    Image:         busybox:latest
    Image ID:      docker-pullable://busybox@sha256:954e1f01e80ce09d0887ff6ea10b13a812cb01932a0781d6b0cc23f743a874fd
    Port:          <none>
    Host Port:     <none>
    Command:
      /bin/sh
      -c
      mkdir -p /usr/share/nginx/html; echo $(date) >> /usr/share/nginx/html/test.html;sleep 3600
    State:          Running
      Started:      Sat, 06 Apr 2019 21:11:07 +0800
    Ready:          True
    Restart Count:  0
    Environment:    <none>
    Mounts:
      /var/run/secrets/kubernetes.io/serviceaccount from default-token-f9699 (ro)
Conditions:
  Type              Status
  Initialized       True 
  Ready             False 
  ContainersReady   False 
  PodScheduled      True 
Volumes:
  default-token-f9699:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  default-token-f9699
    Optional:    false
QoS Class:       BestEffort
Node-Selectors:  <none>
Tolerations:     node.kubernetes.io/not-ready:NoExecute for 300s
                 node.kubernetes.io/unreachable:NoExecute for 300s
Events:
  Type     Reason     Age                  From               Message
  ----     ------     ----                 ----               -------
  Normal   Scheduled  16m                  default-scheduler  Successfully assigned default/tcpsocket-ready-pod to node01
  Normal   Created    16m                  kubelet, node01    Created container myapp
  Normal   Started    16m                  kubelet, node01    Started container myapp
  Normal   Pulled     16m                  kubelet, node01    Container image "ikubernetes/myapp:v1" already present on machine
  Warning  Failed     13m                  kubelet, node01    Failed to pull image "busybox:latest": rpc error: code = Unknown desc = Error response from daemon: Get https://registry-1.docker.io/v2/library/busybox/manifests/latest: read tcp 192.168.48.201:35494->52.22.201.61:443: read: connection reset by peer
  Warning  Failed     11m (x3 over 14m)    kubelet, node01    Error: ErrImagePull
  Warning  Failed     11m (x2 over 14m)    kubelet, node01    Failed to pull image "busybox:latest": rpc error: code = Unknown desc = context canceled
  Warning  Failed     10m (x5 over 14m)    kubelet, node01    Error: ImagePullBackOff
  Normal   BackOff    10m (x5 over 14m)    kubelet, node01    Back-off pulling image "busybox:latest"
  Normal   Pulling    10m (x4 over 16m)    kubelet, node01    Pulling image "busybox:latest"
  Normal   Pulled     10m                  kubelet, node01    Successfully pulled image "busybox:latest"
  Normal   Created    10m                  kubelet, node01    Created container busybox
  Normal   Started    10m                  kubelet, node01    Started container busybox
  Warning  Unhealthy  92s (x8 over 3m52s)  kubelet, node01    Readiness probe failed: dial tcp 10.244.1.6:80: connect: connection refused
隔壁小翔
关注
  • 0
    点赞
  • 踩
  • 1
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
专栏目录
【ubutnu24.04】k8s部署3:重新安装1.31.0并init成功
突围
08-15 157
#!/bin/sh sudo systemctl restart containerd sudo systemctl status containerd
【ubutnu18.04】k8s 部署4: worker节点配置1.31.0和containerd 1.7.20
最新发布
突围
08-16 209
1.31.0并init成功
Kubernetes(8)Health Check
c13891506947的博客
07-05 370
文章目录Kubernetes(8)Health Check基本的健康检查Liveness探测Readiness探测多副本应用时Health Check & Rolling UpdatemaxSurge和maxUnavailable Kubernetes(8)Health Check 强大的自愈能力是Kubernetes这类容器编排引擎的一个重要特性。自愈的默认实现方式是自动重启发生故障的容器。除此之外,用户还可以利用Liveness和Readiness探测机制设置更精细的健康检查,进而实现如下需求
k8s健康检查
认知 行动 坚持
11-19 7253
健康检查概述 健康检查（Health Check）用于检测您的应用实例是否正常工作，是保障业务可用性的一种传统机制，一般用于负载均衡下的业务，如果实例的状态不符合预期，将会把该实例“摘除”，不承担业务流量。 应用在运行过程中难免会出现错误，如程序异常，软件异常，硬件故障，网络故障等。在kubernetes中提供Health Check健康检查机制，当发现应用异常时会自动重启容器，将应用从service服务中剔除，保障应用的高可用性。 k8s健康检查介绍 Kubernetes中的健康检查主要使用存活性探针（l
完美解决HTTP 400错误：“status“: 400, “error“: “Bad Request“
热门推荐
科技改变人类，技术成就未来
06-17 1万+
本文深入解析了HTTP 400错误的常见原因，展示如何调试和解决这个问题，并结合实际代码示例进行说明。关键点总结：1. **检查URL、方法、头信息、请求格式，包括JSON格式**。2. **确保请求体内容和服务器期望的格式一致**。3. **使用调试工具(cURL, Postman)手动测试，逐步排除错误**。4. **增加日志和异常处理，以获取更具体的错误信息**。通过系统化的调试和逐一排查，你将能够有效解决大多数的400错误问题。希望本文对你解决实际问题有所帮助。
k8s的健康性检查-Health Check
最美dee时光的博客
04-30 7254
1、k8s健康性检查的默认方式 k8s默认的健康检查机制：基于Dockerfile文件中的CMD或者ENTRYPOINT，如果进程退出时返回码为非零，则认为容器发生故障，k8s就会根据restartPolicy重启容器。 1）docker的restartPolicy有一下4种： always：（无论以什么码退出，docker daemon都会尝试重启退出的容器，手动停止后，策略不再生效）； ...
玩转k8s（六）—— Health Check健康检查
weixin_49561506的博客
03-18 1871
介绍了K8S健康检查的两种机制：Liveness探测和Readiness探测。
k8s系列之七Health Check
ByteX的博客
01-31 1235
强大的自愈能力是Kubernetes这类容器编排引擎的⼀个重要特性。自愈的默认实现方式是自动重启发生故障的容器。除此之外，用户还可以利用Liveness和Readiness探测机制设置更精细的健康检查，进而实现：（1）零停机部署。（2）避免部署无效的镜像。（3）更加安全的滚动升级。
mysql容器 重启_Docker容器和K8s添加Health Check
weixin_39977934的博客
11-20 648
目录Dockerfile中添加Health CheckHealth check在docker-compose.yml中的配置Docker lib官方health check示例K8s中的健康检查Container ExecHTTP Health CheckTCP Socketreadiness 检查实例参考docker容器启动后，怎么确认容器运行正常，怎么确认可以对外提供服务了，这就需要...
深入浅出学K8s（二十一）- 解密｜K8s保障集群的灾备和恢复
weixin_39552004的博客
08-28 2297
云世 公众号 推荐使用以下关键字搜索 云世 公众号获取更多K8s系列课程： 「k8s集群灾备、etcd备份、pv备份、云原生集群灾备、恢复集群灾备」 Kubernetes 隐藏了所有容器编排的复杂细节，让我们可以专注在应用本身，而无须过多关注如何去做部署和维护。此外，Kubernetes 还支持多副本，可以保证我们业务的高可用性。而对于集群本身而言，我们一样也要保证其高可用性。 但是这些并不足以让我们高枕无忧，因为Kubernetes 在帮助我们编排调度容器的同时，往往还保存了很多...
一步步学习k8s(一)
中國颜值半壁江山的博客
03-15 489
1、目前使用docker的情况 使用docker的缺点： 使用Docker容器化封装应用程序的缺点(坏处) 单机使用，无法有效集群 随着容器数量的上升，管理成本攀升 没有有效的容灾/自愈机制 没有预设编排模板，无法实现快速、大规模容器调度 没有统一的配置管理中心工具 没有容器生命周期的管理工具 没有图形化运维管理工具 使用Docker容器化封装应用程序的意义(好处) Docker引擎统一了基础设施环境-docker环境 硬件的配置 操作系统的版本 运行时环境的异构 Docker引擎统一了程序打包
k8s的Health Check（健康检查）
weixin_30885111的博客
11-10 2929
强大的自愈能力是 Kubernetes 这类容器编排引擎的一个重要特性。自愈的默认实现方式是自动重启发生故障的容器。除此之外，用户还可以利用 Liveness 和 Readiness 探测机制设置更精细的健康检查，进而实现如下需求： 零停机部署。 避免部署无效的镜像。 更加安全的滚动升级。 下面通过实践学习 Kubernetes 的 Health Check...
十一、K8s 健康性检查
tushanpeipei的博客
07-08 3419
概述： 健康检查（Health Check）用于检测应用实例是否正常工作（例如某pod中文件丢失了，但是状态还是running，这种情况下deployment无法查看），是保障业务可用性的一种传统机制，一般用于负载均衡下的业务，如果实例的状态不符合预期，将会把该实例“摘除”，不承担业务流量。 Kubernetes中的健康检查使用存活性探针（liveness probes）和就绪性探针（readiness probes）来实现，service即为负载均衡，k8s保证 service 后面的 pod 都可用，是
Kubernetes | Health Check
weixin_37417954的博客
10-10 786
                       --昨夜西风凋碧树，独上高楼，望尽天涯路 自愈能力是Kubernetes一个强大的特性，自愈的默认实现方式是自动重启发生故障的容器，除此之外，还可以利用Liveness和Readiness探测机制设置更精细的健康检查。 有了这个强大的特性可以实现强大的需求： 1）零停机部署 2）避免部署无效镜像 3）更加安全的滚动升级 默认健康检测 ...
k8s健康检查（七）_normal scheduled 15s default-scheduler successfull
2401_84253182的博客
04-13 646
外链图片转存中…(img-lrNmfWVT-1712974865371)]
k8s——滚动更新与 Health Check
weixin_44848382的博客
07-21 784
k8s——滚动更新与 Health CheckRolling Update回滚Health Check默认的健康检查Liveness 探测Readiness 探测Liveness 与 Readiness 的区别：在Scale Up中使用 Health Check在滚动更新中使用Health Check Rolling Update 下面我们部署三个副本应用，初始镜像为 httpd：2.2，然后将其更新到 httpd：2.4 编写 httpd：2.2 配置文件： [root@master service]
Health Check(kubernetes)
qq_27069821的博客
07-25 579
Health Check(Probe) Health Check(Probe)称为健康检查，用于检查pod是否处于健康状态，若处于非健康状态，则会重新启动container，分为readiness probes和liveness probes。 Liveness Probes(存活探针) 虚拟机时期，当一个服务由于某些原因down了，比如oom，此时，只能等运维人员接收到告警或者用户投诉才会知道服务挂掉了，然后再登录到机器上，手动启动该服务，这样不仅加重了运维人员的工作量，并且就算能够重启，在重启前的这一段
【Kubernetes】k8s的健康性检查详细说明【livenss probe、readiness probe】
崔崇鑫的博客，你linux/云运维工作中的百科全书。
09-06 7228
文章目录探测的目的环境准备什么是 Container Probes健康状态说明yaml配置文件参数说明perbe功能前测试liveness probecommandhttpGettcpSocketreadiness probecommandhttpGettcpSocket 探测的目的 deployment的作用 用来维持 pod的健壮性 当pod挂掉之后，deployment会生成新的pod 但如果pod是正常运行的，但pod里面出了问题，此时deployment是监测不到的。 故此需要探测（pro
【K8S】健康检查初探
阳阳的博客
01-03 1324
健康检查的意义 为了保证集群的稳定性，需要及时的对故障服务进行处理。无论是通过下线的方式，不再将请求转发到该服务，还是通过重启的方式，使服务得以自动恢复，都是有效的处理方式。 健康检查的策略 而如何检测出服务是否有故障，k8s提供了以下的健康检查策略。 livenessProbe 存活性探针 readinessProbe 就绪性探针 livenessPr...
写一个k8smysql.yaml
02-23
name: k8s-mysql spec: selector: matchLabels: app: k8s-mysql replicas: 1 template: metadata: labels: app: k8s-mysql spec: containers: - name: k8s-mysql image: mysql:5.7 ports: - ...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值