Déployer des applications Kubernetes sur Google Cloud : atelier challenge avis
104395 avis
Vishal G. · Examiné il y a environ un an
Venkatesh P. · Examiné il y a environ un an
Govardhana Bangaru D. · Examiné il y a environ un an
Richard M. · Examiné il y a environ un an
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. · Examiné il y a environ un an
Ajith R. · Examiné il y a environ un an
Lukas E. · Examiné il y a environ un an
Good.
Spidy G. · Examiné il y a environ un an
Naveen R. · Examiné il y a environ un an
Mohanasundaram N. · Examiné il y a environ un an
Ved V. · Examiné il y a environ un an
Noah X. · Examiné il y a environ un an
Takahide M. · Examiné il y a environ un an
Takahide M. · Examiné il y a environ un an
Luis S. · Examiné il y a environ un an
Piotr K. · Examiné il y a environ un an
Colin B. · Examiné il y a environ un an
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. · Examiné il y a environ un an
good
Hariprasath N. · Examiné il y a environ un an
I catched an error "denied: This API method requires billing to be enabled. Please enable billing on project #326819031181 by visiting https://console.developers.google.com/billing/enable?project=326819031181 then retry. If you enabled billing for this project recently, wait a few minutes for the action to propagate to our systems and retry." and didn't finish the lab
Віталій Г. · Examiné il y a environ un an
I catched an error "denied: This API method requires billing to be enabled. Please enable billing on project #326819031181 by visiting https://console.developers.google.com/billing/enable?project=326819031181 then retry. If you enabled billing for this project recently, wait a few minutes for the action to propagate to our systems and retry." and didn't finish the lab
Віталій Г. · Examiné il y a environ un an
Rushikesh P. · Examiné il y a environ un an
Koichiro O. · Examiné il y a environ un an
Adam D. · Examiné il y a environ un an
Ivar M. · Examiné il y a environ un an
Nous ne pouvons pas certifier que les avis publiés proviennent de consommateurs qui ont acheté ou utilisé les produits. Les avis ne sont pas vérifiés par Google.