Deploy Kubernetes Applications on Google Cloud: Challenge Lab Reviews

Daniel K. · Reviewed 7 months ago

very good

Rahul M. · Reviewed 7 months ago

I did all steps and see services up and running but "Check my progress" didn't see my progress

Віталій Г. · Reviewed 7 months ago

jhvhjv

Rahul M. · Reviewed 7 months ago

Ronaldo M. · Reviewed 7 months ago

Daniel H. · Reviewed 7 months ago

Federico K. · Reviewed 7 months ago

Vishal G. · Reviewed 7 months ago

Venkatesh P. · Reviewed 7 months ago

Govardhana Bangaru D. · Reviewed 7 months ago

Richard M. · Reviewed 7 months ago

The app is up and running and the last checkpoint throws error with a message that the service endpoint must be created and it already is created and working

Federico K. · Reviewed 7 months ago

Ajith R. · Reviewed 7 months ago

Lukas E. · Reviewed 7 months ago

Good.

Spidy G. · Reviewed 7 months ago

Naveen R. · Reviewed 7 months ago

Mohanasundaram N. · Reviewed 7 months ago

Ved V. · Reviewed 7 months ago

Noah X. · Reviewed 7 months ago

Takahide M. · Reviewed 7 months ago

Takahide M. · Reviewed 7 months ago

Luis S. · Reviewed 7 months ago

Piotr K. · Reviewed 7 months ago

Colin B. · Reviewed 7 months ago

This lab is very helpful in learning the basics of Kubernetes and how to deploy Kubernetes applications on Google Cloud. In particular, the fact that it assumes knowledge of Docker learned in previous labs is important for facilitating smooth learning. However, be careful with docker image tagging. In a previous attempt, I tagged the image in the format "name/tag" instead of "name:tag", and even though I progressed to Task 4, the service itself appeared to be functioning normally. However, I failed the final challenge. It was during the retry that I realized that the cause of this was the incorrect tagging. From this experience, I recommend paying attention to the following two points: 1. docker image tagging format: The correct tagging format is "name:tag". Although it is possible to proceed to Task 4 even with the "name/tag" format, it can cause the final challenge to fail, so be sure to use the "name:tag" format. 2. Confirmation upon challenge failure: If you fail a challenge, don't panic, and try to identify where you failed, check for error messages, etc. In this case, the docker image tagging may be the cause.

Takashi S. · Reviewed 7 months ago