Stale image in "Configure Liveness, Readiness and Startup Probes"

[harshitsahu2311]

In this document the yaml file for liveness probe using registry.k8s.io/busybox is showing depricated, but as I used busybox official image it is running as expected outputs.

[sftim]

/retitle Stale image in "Configure Liveness, Readiness and Startup Probes"
/language en

[sftim]

I think this issue is about https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/

[sftim]

Assuming that we stick with Busybox:

• we should pin to a specific busybox image version
• we should make sure to use a current container image for Busybox (doesn't have to come from registry.k8s.io)

[sftim]

/kind bug
/triage accepted

[iheartNathan]

@harshitsahu2311 where are you getting this deprecated message for registry.k8s.io/busybox?
image: registry.k8s.io/busybox is pulling the lastest tag for busybox

    containerStatuses:
    - containerID: containerd://0c37f27fe26d9746aad3c356540355da531ab52f5a3dea2d49b7cbdc8fa47133
      image: registry.k8s.io/busybox:latest
      imageID: sha256:36a4dca0fe6fb2a5133dc11a6c8907a97aea122613fa3e98be033959a0821a1f

$ crane ls registry.k8s.io/busybox --full-ref
registry.k8s.io/busybox:1.24
registry.k8s.io/busybox:1.27
registry.k8s.io/busybox:1.27.2
registry.k8s.io/busybox:latest

The container is killed and recreated based on the failed liveness probe check as expected.

Events:
  Type     Reason     Age                  From               Message
  ----     ------     ----                 ----               -------
  Normal   Scheduled  4m8s                 default-scheduler  Successfully assigned default/liveness-exec to node01
  Normal   Pulled     4m7s                 kubelet            Successfully pulled image "registry.k8s.io/busybox" in 593ms (593ms including waiting). Image size: 1144547 bytes.
  Normal   Pulled     2m52s                kubelet            Successfully pulled image "registry.k8s.io/busybox" in 595ms (595ms including waiting). Image size: 1144547 bytes.
  Normal   Created    97s (x3 over 4m7s)   kubelet            Created container liveness
  Normal   Started    97s (x3 over 4m7s)   kubelet            Started container liveness
  Normal   Pulled     97s                  kubelet            Successfully pulled image "registry.k8s.io/busybox" in 551ms (551ms including waiting). Image size: 1144547 bytes.
  Warning  Unhealthy  53s (x9 over 3m33s)  kubelet            Liveness probe failed: cat: can't open '/tmp/healthy': No such file or directory
  Normal   Killing    53s (x3 over 3m23s)  kubelet            Container liveness failed liveness probe, will be restarted
  Normal   Pulling    23s (x4 over 4m8s)   kubelet            Pulling image "registry.k8s.io/busybox"

k get po --watch
NAME            READY   STATUS    RESTARTS   AGE
liveness-exec   1/1     Running   0          3s
liveness-exec   1/1     Running   1 (1s ago)   76s
liveness-exec   1/1     Running   2 (2s ago)   2m32s
liveness-exec   1/1     Running   3 (2s ago)   3m47s

[harshitsahu2311]

When I was trying to execute this manifest , I was getting an error message on minikube cluster and pod was also on Pending State

[iheartNathan]

@harshitsahu2311 Thanks.
I was testing in Killercoda and Kind. I'm getting ImagePullBackOff testing on a Docker Desktop Kubernetes cluster, are you using Docker as the driver for your minikube cluster?

Events:
  Type     Reason     Age                From               Message
  ----     ------     ----               ----               -------
  Normal   Pulling    22s (x2 over 39s)  kubelet            Pulling image "registry.k8s.io/busybox"
  Warning  Failed     21s (x2 over 38s)  kubelet            Failed to pull image "registry.k8s.io/busybox": Error response from daemon: [DEPRECATION NOTICE] Docker Image Format v1 and Docker Image manifest version 2, schema 1 support is disabled by default and will be removed in an upcoming release. Suggest the author of registry.k8s.io/busybox:latest to upgrade the image to the OCI Format or Docker Image manifest v2, schema 2. More information at https://docs.docker.com/go/deprecated-image-specs/
  Warning  Failed     21s (x2 over 38s)  kubelet            Error: ErrImagePull
  Normal   BackOff    10s (x4 over 37s)  kubelet            Back-off pulling image "registry.k8s.io/busybox"
  Warning  Failed     10s (x4 over 37s)  kubelet            Error: ImagePullBackOff

Looks like registry.k8s.io/busybox:latest is using a deprecated image format.

[harshitsahu2311]

Yes, I was using docker as the driver for minikube cluster, Is it coming due to this driver??

[iheartNathan]

OK, registry.k8s.io/busybox:1.27 and registry.k8s.io/busybox:1.27.2 are in the current supported format.
We might have to update the docs to use any of these images.

[iheartNathan]

/assign

[iheartNathan]

@harshitsahu2311 has to do with the image format of registry.k8s.io/busybox:lastest

[harshitsahu2311]

Yes this image is right now, My name can also be mentioned on contributors list?