Implement DevOps Workflows in Google Cloud: Challenge Lab Reviews

Eric B. · Reviewed about 3 years ago

Chandan B. · Reviewed about 3 years ago

Denys H. · Reviewed about 3 years ago

Manuel I. · Reviewed about 3 years ago

Cloning into 'sample-app'... warning: You appear to have cloned an empty repository. sample-app Cloning into 'sample-app'... warning: You appear to have cloned an empty repository.

Julio T. · Reviewed about 3 years ago

Сергій Х. · Reviewed about 3 years ago

Tomek J. · Reviewed about 3 years ago

not enough info from prev labs,

Anton B. · Reviewed about 3 years ago

Kalle-Ville K. · Reviewed about 3 years ago

Kalle-Ville K. · Reviewed about 3 years ago

The last step roll back check unsuccessful if you make rollout with command "kubectl rollout undo". The only way is to edit deployment with v1.0 version.

ALEKSEI G. · Reviewed about 3 years ago

Anton B. · Reviewed about 3 years ago

zack w. · Reviewed about 3 years ago

Yaay, I really enjoyed this and just learning it. I have to repeat it.

Tibor O. · Reviewed about 3 years ago

the project id inside the deployment.yaml file shall also be updated, otherwise the image url is not set correct

Yingding W. · Reviewed about 3 years ago

Oleksandr R. · Reviewed about 3 years ago

Task 2, p.5 has an annoying description that does not correspond to what Git as a program does. "Create a branch named dev. Make a commit with the sample code added to your sample-app directory and push the changes to the dev branch." If you create a new branch, it will be based off whatever branches you have created already, therefore you can't quite 'make a commit' to add the already added code. It would be much more consistent to say here "Create new branch 'dev' based on the commit in the 'master' branch."

Pavel K. · Reviewed about 3 years ago

Muhammed A. · Reviewed about 3 years ago

Simone C. · Reviewed about 3 years ago

Vladyslav P. · Reviewed about 3 years ago

can't connect to this lab

Vladyslav P. · Reviewed about 3 years ago

Lab has finally been fixed!

Rocky L. · Reviewed about 3 years ago

Wagner V. · Reviewed about 3 years ago

bad, You can explore the component files directly from the repository. You can examine the Kubernetes manifest templates for the three types of deployment (production, canary, and dev) in the sample-app/k8s directory. => already used 14credits but there are no manifest templates, sample-app is empty

Alexey P. · Reviewed about 3 years ago