Exploring Cost-optimization for GKE Virtual Machines Reviews

32776 reviews

Please update the pod definition with containers actually including the shell. Also the last check did not work correctly while "k get pods -o wide" already showed all pods running and on the same node.

Simon M. · Reviewed почти 4 лет ago

kubectl exec -it pod-1 -- sh is not working

sachin m. · Reviewed почти 4 лет ago

- kubectl exec -it pod-1 -- sh doesn't work - the last check never succeeds

Taku K. · Reviewed почти 4 лет ago

Taku K. · Reviewed почти 4 лет ago

Piyush R. · Reviewed почти 4 лет ago

Pengkuh D. · Reviewed почти 4 лет ago

Mohan Krishna A. · Reviewed почти 4 лет ago

Basavaraj H. · Reviewed почти 4 лет 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 почти 4 лет ago

ALOK K. · Reviewed почти 4 лет 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 почти 4 лет ago

Chun-Te S. · Reviewed почти 4 лет ago

Amasidda L. · Reviewed почти 4 лет ago

Mohit B. · Reviewed почти 4 лет 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 почти 4 лет ago

Mohan Krishna A. · Reviewed почти 4 лет ago

Pushpanjali S. · Reviewed почти 4 лет ago

Weichen L. · Reviewed почти 4 лет ago

Vignesh R. · Reviewed почти 4 лет ago

Boran L. · Reviewed почти 4 лет ago

Robin S. · Reviewed почти 4 лет ago

Sujnana R. · Reviewed почти 4 лет ago

Vivek B. · Reviewed почти 4 лет 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 почти 4 лет ago

Tom P. · Reviewed почти 4 лет ago

We do not ensure the published reviews originate from consumers who have purchased or used the products. Reviews are not verified by Google.