Exploring Cost-optimization for GKE Virtual Machines Reviews

Pengkuh D. · Reviewed около 3 лет ago

Mohan Krishna A. · Reviewed около 3 лет ago

Basavaraj H. · Reviewed около 3 лет ago

Problem with latest pod 1 image. Also even if you use old images, traffic simulation fails when you can see traffic in logs. Problem with this assignment, can be completed only 90%.

Bhushan N. · Reviewed около 3 лет ago

ALOK K. · Reviewed около 3 лет ago

The command kubectl exec -it pod-1 -- sh wouldn't execute and said error: Internal error occured: error executing command in container: failed to exec in container: failed to start exec "7ab..." It's almost funny how many random occurs occur throughout these qwiklabs making them impossible to get 100% on

Brenden A. · Reviewed около 3 лет ago

Chun-Te S. · Reviewed около 3 лет ago

Amasidda L. · Reviewed около 3 лет ago

Mohit B. · Reviewed около 3 лет ago

Problem with pod 1 exec command. OCI error from gcloud is not allowing me to complete this lab. Taken multiple times. This is container software version issue. Please help correct it.

Bhushan N. · Reviewed около 3 лет ago

Mohan Krishna A. · Reviewed около 3 лет ago

Pushpanjali S. · Reviewed около 3 лет ago

Weichen L. · Reviewed около 3 лет ago

Vignesh R. · Reviewed около 3 лет ago

Boran L. · Reviewed около 3 лет ago

Robin S. · Reviewed около 3 лет ago

Sujnana R. · Reviewed около 3 лет ago

Vivek B. · Reviewed около 3 лет ago

Scale up task: the task expected not having enough resources but actually I had enough. Needed to scale up to 3 pods to receive the expected error message. SH is not available on pod-1: student_02_1f75c7827c27@cloudshell:~ (qwiklabs-gcp-01-97f67d841871)$ kubectl exec -it pod-1 -- sh error: Internal error occurred: error executing command in container: failed to exec in container: failed to start exec "3043c4805c0cf0cc7411d94b9a05a249125efbbee04a7e74a7a16e4a2f62f80d": OCI runtime exec failed: exec failed: unable to start container process: exec: "sh": executable file not found in $PATH: unknown But it is available for pod-2: student_02_1f75c7827c27@cloudshell:~ (qwiklabs-gcp-01-97f67d841871)$ kubectl exec -it pod-2 -- sh # ping 10.60.0.9 PING 10.60.0.9 (10.60.0.9): 56 data bytes 64 bytes from 10.60.0.9: icmp_seq=0 ttl=62 time=1.822 ms 64 bytes from 10.60.0.9: icmp_seq=1 ttl=62 time=0.417 ms 64 bytes from 10.60.0.9: icmp_seq=2 ttl=62 time=0.417 ms 64 bytes from 10.60.0.9: icmp_seq=3 ttl=62 time=0.422 ms You cannot ping a port number: # ping 10.60.0.9:8080 ping: unknown host

István A. · Reviewed около 3 лет ago

Tom P. · Reviewed около 3 лет ago

P N V KRISHNA T. · Reviewed около 3 лет ago

There is an issue in GCP side. hence not able to complete this lab

ramesh b. · Reviewed около 3 лет ago

Willie S. · Reviewed около 3 лет ago

in the task3 environment is not working such as shell is not opening for pod1

ALOK K. · Reviewed около 3 лет ago

Cannot exec into pod-1, it doesn't have sh and to run ping on pod-2, and last check keeps failing at sink creation, even y retried to create it multiple times. And I think that "ping ip:port" is not supported, you need another tool for that.

Federico T. · Reviewed около 3 лет ago