Configuring Liveness and Readiness Probes Reviews

오승희 S. · Reviewed over 3 years ago

Ron S. · Reviewed over 3 years ago

Shiyuan W. · Reviewed over 3 years ago

Aungon Nag R. · Reviewed over 3 years ago

LEONID C. · Reviewed over 3 years ago

varun T. · Reviewed over 3 years ago

The manifest `readiness-deployment.yaml` fails with CrashLoopBackoff

Tom B. · Reviewed over 3 years ago

rakesh kumar reddy a. · Reviewed over 3 years ago

Lyubomir S. · Reviewed over 3 years ago

The hello-image on the readiness deployment caused the CrashloopBackOff error while describing or getting the pod status.

Poornima K. · Reviewed over 3 years ago

The hello-web image has been broken since it's last update, with no access to /bin/sh, so Task 3 fails with a CrashLoopBackOff error

Tim B. · Reviewed over 3 years ago

The image had an error (/bin/sh not available ) so an earlier version had to be used

Andrew B. · Reviewed over 3 years ago

Image is broken for readiness-deployment

Rahul R. · Reviewed over 3 years ago

Aniruddha S. · Reviewed over 3 years ago

Epic failure - base image changed in container image

Mark R. · Reviewed over 3 years ago

Richard W. · Reviewed over 3 years ago

The container image (gcr.io/google-samples/hello-app:1.0) describe failed to start Normal Scheduled 20s default-scheduler Successfully assigned default/readiness-deployment-6b5ccdd8d7-ghgtr to gke-standard-cluster-standard-cluster-c038b6e2-769l Normal Pulled 2s (x3 over 19s) kubelet Container image "gcr.io/google-samples/hello-app:1.0" already present on machine Normal Created 2s (x3 over 19s) kubelet Created container readiness Warning Failed 2s (x3 over 19s) kubelet Error: failed to create containerd task: failed to create shim: OCI runtime create failed: runc create failed: unable to start container process: exec: "/bin/sh": stat /bin/sh: no such file or directory: unknown Warning BackOff 0s (x7 over 18s) kubelet Back-off restarting failed container

Bryan S. · Reviewed over 3 years ago

Brayan G. · Reviewed over 3 years ago

Tianjun F. · Reviewed over 3 years ago

.yaml for 2nd exercise is not working as expected

Edgar S. · Reviewed over 3 years ago

Inho K. · Reviewed over 3 years ago

Seokho S. · Reviewed over 3 years ago

tonyhan G. · Reviewed over 3 years ago

고영국 S. · Reviewed over 3 years ago

박진홍 박. · Reviewed over 3 years ago