sample outputs created working with Kubernetes v1.24 without docker (#31454)

* sample outputs created without docker working with kubernetes v1.24

* updated

* cleaned and updated

* sample outputs created without docker working with kubernetes v1.24

* updated

* cleaned and updated
pull/32514/head
Subhasmita Swain 2022-03-26 05:47:58 +05:30 committed by GitHub
parent 185512f752
commit 09f8637c05
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 16 additions and 15 deletions

View File

@ -81,13 +81,13 @@ kubectl describe pod liveness-exec
The output indicates that no liveness probes have failed yet: The output indicates that no liveness probes have failed yet:
``` ```
FirstSeen LastSeen Count From SubobjectPath Type Reason Message Type Reason Age From Message
--------- -------- ----- ---- ------------- -------- ------ ------- ---- ------ ---- ---- -------
24s 24s 1 {default-scheduler } Normal Scheduled Successfully assigned liveness-exec to worker0 Normal Scheduled 11s default-scheduler Successfully assigned default/liveness-exec to node01
23s 23s 1 {kubelet worker0} spec.containers{liveness} Normal Pulling pulling image "k8s.gcr.io/busybox" Normal Pulling 9s kubelet, node01 Pulling image "k8s.gcr.io/busybox"
23s 23s 1 {kubelet worker0} spec.containers{liveness} Normal Pulled Successfully pulled image "k8s.gcr.io/busybox" Normal Pulled 7s kubelet, node01 Successfully pulled image "k8s.gcr.io/busybox"
23s 23s 1 {kubelet worker0} spec.containers{liveness} Normal Created Created container with docker id 86849c15382e; Security:[seccomp=unconfined] Normal Created 7s kubelet, node01 Created container liveness
23s 23s 1 {kubelet worker0} spec.containers{liveness} Normal Started Started container with docker id 86849c15382e Normal Started 7s kubelet, node01 Started container liveness
``` ```
After 35 seconds, view the Pod events again: After 35 seconds, view the Pod events again:
@ -100,14 +100,15 @@ At the bottom of the output, there are messages indicating that the liveness
probes have failed, and the containers have been killed and recreated. probes have failed, and the containers have been killed and recreated.
``` ```
FirstSeen LastSeen Count From SubobjectPath Type Reason Message Type Reason Age From Message
--------- -------- ----- ---- ------------- -------- ------ ------- ---- ------ ---- ---- -------
37s 37s 1 {default-scheduler } Normal Scheduled Successfully assigned liveness-exec to worker0 Normal Scheduled 57s default-scheduler Successfully assigned default/liveness-exec to node01
36s 36s 1 {kubelet worker0} spec.containers{liveness} Normal Pulling pulling image "k8s.gcr.io/busybox" Normal Pulling 55s kubelet, node01 Pulling image "k8s.gcr.io/busybox"
36s 36s 1 {kubelet worker0} spec.containers{liveness} Normal Pulled Successfully pulled image "k8s.gcr.io/busybox" Normal Pulled 53s kubelet, node01 Successfully pulled image "k8s.gcr.io/busybox"
36s 36s 1 {kubelet worker0} spec.containers{liveness} Normal Created Created container with docker id 86849c15382e; Security:[seccomp=unconfined] Normal Created 53s kubelet, node01 Created container liveness
36s 36s 1 {kubelet worker0} spec.containers{liveness} Normal Started Started container with docker id 86849c15382e Normal Started 53s kubelet, node01 Started container liveness
2s 2s 1 {kubelet worker0} spec.containers{liveness} Warning Unhealthy Liveness probe failed: cat: can't open '/tmp/healthy': No such file or directory Warning Unhealthy 10s (x3 over 20s) kubelet, node01 Liveness probe failed: cat: can't open '/tmp/healthy': No such file or directory
Normal Killing 10s kubelet, node01 Container liveness failed liveness probe, will be restarted
``` ```
Wait another 30 seconds, and verify that the container has been restarted: Wait another 30 seconds, and verify that the container has been restarted: