关于“Configuring Google Kubernetes Engine (GKE) Networking”的评价

not so well destribed, can make errors in the create task

Peter G. · 评论almost 6 years之前

Stefan G. · 评论almost 6 years之前

Dennis K. · 评论almost 6 years之前

The description of the first part was not so good.

Heiko W. · 评论almost 6 years之前

Ingmar M. · 评论almost 6 years之前

Steps in "Create a private cluster" do not mach the webgui.

Dirk L. · 评论almost 6 years之前

Instruction in the first part were unclear. (Creating the cluster) Description doesn't match the GUI

Sebastian L. · 评论almost 6 years之前

André S. · 评论almost 6 years之前

Yannick R. · 评论almost 6 years之前

Attapol T. · 评论almost 6 years之前

praveen g. · 评论almost 6 years之前

Ketan P. · 评论almost 6 years之前

good

Alexander P. · 评论almost 6 years之前

Aadesh K. · 评论almost 6 years之前

hardik h. · 评论almost 6 years之前

In the last step of the lab, to verify egress, the alpine test-3 image never offered a command prompt. I tried restarting the test-3 pod several times, and compared commandline syntax with previous alpine pod invocations during the lab. As a last attempt, I tried the same using ubuntu. I noticed the qwiklab/coursera response time today was slow - perhaps it was due to high utilization?

Kathy D. · 评论almost 6 years之前

Sean C. · 评论almost 6 years之前

Kibaek J. · 评论almost 6 years之前

herfiedhantya b. · 评论almost 6 years之前

Moumouwan M. · 评论almost 6 years之前

Sudhir S. · 评论almost 6 years之前

you need to update 1st explanation to make cluster.

Daehan C. · 评论almost 6 years之前

hoyoung k. · 评论almost 6 years之前

The command: kubectl run test-3 --labels app=foo --image=alpine --restart=Never --rm --stdin --tty did not result in a command prompt even after hitting enter. Doing a kubectl describe pods test-3 resulted in an Event: FailedScheduling 4s (x4 over 2m42s) default-scheduler 0/2 nodes are available: 2 Insufficient cpu.

Erly T. · 评论almost 6 years之前

Ajay D. · 评论almost 6 years之前