Creating Services and Ingress Resources Reviews

Ratna P. · Reviewed over 5 years ago

Brij M. · Reviewed over 5 years ago

Rushali V. · Reviewed over 5 years ago

Nishith G. · Reviewed over 5 years ago

Dmytro V. · Reviewed over 5 years ago

Mark W. · Reviewed over 5 years ago

lahiru n. · Reviewed over 5 years ago

Floyd S. · Reviewed over 5 years ago

Rohan S. · Reviewed over 5 years ago

Mark S. · Reviewed over 5 years ago

Failure in Task 7 with v1 backend service not receiving requests from the Ingress.

Volkan P. · Reviewed over 5 years ago

Alessandro G. · Reviewed over 5 years ago

There is a bug - limits of CPU allows only to create 2 replicas of hello-v2.

Kamil S. · Reviewed over 5 years ago

Berkay B. · Reviewed over 5 years ago

There is a bug in this lab, once every pods are deployed we reach the cpu limit for the lab. Scaling out the hello-v2 deployment to 1 solves the issues. It will be better to decrease the number of replicas in hello-v1 and hello-v2 in the yaml deployment definition to not reach the limit

Mohammed M. · Reviewed over 5 years ago

Nathan S. · Reviewed over 5 years ago

Dor A. · Reviewed over 5 years ago

Great

Ariful I. · Reviewed over 5 years ago

Bhupal Singh K. · Reviewed over 5 years ago

Abhinav S. · Reviewed over 5 years ago

Alberto C. · Reviewed over 5 years ago

David M. · Reviewed over 5 years ago

Good lab but I think all regular commands such as git, ln cd ... could be factorize in a script since the value of the lab in these commands. Also, the progress checking is not always sync and I should click a few times to have a green tick. Last thing is about the end of the lab with the ingress load balancer, the last curl commands with v1/v2 were not working in my case (got 404 error).

Thibaut D. · Reviewed over 5 years ago

The error you get while waiting for propagation of the ingress makes you unsure of the fact that you succeeded or not

Romain D. · Reviewed over 5 years ago

Youshu L. · Reviewed over 5 years ago