关于“在 Google Cloud 部署 Kubernetes 應用程式：挑戰實驗室”的评价

very good

Rahul M. · 评论about 1 year之前

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

Віталій Г. · 评论about 1 year之前

jhvhjv

Rahul M. · 评论about 1 year之前

Ronaldo M. · 评论about 1 year之前

Daniel H. · 评论about 1 year之前

Federico K. · 评论about 1 year之前

Vishal G. · 评论about 1 year之前

Venkatesh P. · 评论about 1 year之前

Govardhana Bangaru D. · 评论about 1 year之前

Richard M. · 评论about 1 year之前

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. · 评论about 1 year之前

Ajith R. · 评论about 1 year之前

Lukas E. · 评论about 1 year之前

Good.

Spidy G. · 评论about 1 year之前

Naveen R. · 评论about 1 year之前

Mohanasundaram N. · 评论about 1 year之前

Ved V. · 评论about 1 year之前

Noah X. · 评论about 1 year之前

Takahide M. · 评论about 1 year之前

Takahide M. · 评论about 1 year之前

Luis S. · 评论about 1 year之前

Piotr K. · 评论about 1 year之前

Colin B. · 评论about 1 year之前

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. · 评论about 1 year之前

good

Hariprasath N. · 评论about 1 year之前