Configuring Google Kubernetes Engine (GKE) Networking avis

could not run step 'kubectl run test-3' my cluster with 2 nodes was to small and I had to increas the number of nodes (to6) then it worked

Rolf K. · Examiné il y a presque 6 ans

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

Peter G. · Examiné il y a presque 6 ans

Stefan G. · Examiné il y a presque 6 ans

Dennis K. · Examiné il y a presque 6 ans

The description of the first part was not so good.

Heiko W. · Examiné il y a presque 6 ans

Ingmar M. · Examiné il y a presque 6 ans

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

Dirk L. · Examiné il y a presque 6 ans

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

Sebastian L. · Examiné il y a presque 6 ans

André S. · Examiné il y a presque 6 ans

Yannick R. · Examiné il y a presque 6 ans

Attapol T. · Examiné il y a presque 6 ans

praveen g. · Examiné il y a presque 6 ans

Ketan P. · Examiné il y a presque 6 ans

good

Alexander P. · Examiné il y a presque 6 ans

Aadesh K. · Examiné il y a presque 6 ans

hardik h. · Examiné il y a presque 6 ans

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. · Examiné il y a presque 6 ans

Sean C. · Examiné il y a presque 6 ans

Kibaek J. · Examiné il y a presque 6 ans

herfiedhantya b. · Examiné il y a presque 6 ans

Moumouwan M. · Examiné il y a presque 6 ans

Sudhir S. · Examiné il y a presque 6 ans

you need to update 1st explanation to make cluster.

Daehan C. · Examiné il y a presque 6 ans

hoyoung k. · Examiné il y a presque 6 ans

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. · Examiné il y a presque 6 ans