Exploring Cost-optimization for GKE Virtual Machines Reviews

Pranav A. · Reviewed أكثر من 3 سنوات ago

GSP767 - Exploring Cost-optimization for GKE Virtual Machines I think there is an error in Task 3. Managing a regional cluster In Simulate traffic, I cannot get a shell for the pod-1 container using the command (kubectl exec -it pod-1 -- sh). I tried multiple times but unable to get a shell and because of this I am unable to finish the lab. Please look into the issue and let me know the if there is any error and please provide me the solution. My Email is mozohaibkh@gmail.com Waiting for your response. Thank you.

Mohammad K. · Reviewed أكثر من 3 سنوات ago

Madusanka L. · Reviewed أكثر من 3 سنوات ago

Mohammad K. · Reviewed أكثر من 3 سنوات ago

Влад Д. · Reviewed أكثر من 3 سنوات ago

Cesar D. · Reviewed أكثر من 3 سنوات ago

Aisyah 1. · Reviewed أكثر من 3 سنوات ago

pod-1 do not have sh

Piotr B. · Reviewed أكثر من 3 سنوات ago

nice

Sagar B. · Reviewed أكثر من 3 سنوات ago

Aben Liangliang L. · Reviewed أكثر من 3 سنوات ago

Chinmay Govind B. · Reviewed أكثر من 3 سنوات ago

Sundarraj J. · Reviewed أكثر من 3 سنوات ago

Fabrizio M. · Reviewed أكثر من 3 سنوات ago

SERHII D. · Reviewed أكثر من 3 سنوات ago

Zhandy Z. · Reviewed أكثر من 3 سنوات ago

Neftali Enrique . · Reviewed أكثر من 3 سنوات ago

Bhaskar G. · Reviewed أكثر من 3 سنوات ago

Mostafa R. · Reviewed أكثر من 3 سنوات ago

Nobel T. · Reviewed أكثر من 3 سنوات ago

the first pod didn't have sh and I needed to ping from pod 2 the first one.

Zsolt T. · Reviewed أكثر من 3 سنوات ago

Gonçalo C. · Reviewed أكثر من 3 سنوات ago

Olga P. · Reviewed أكثر من 3 سنوات ago

student_03_5217e47b779d@cloudshell:~ (qwiklabs-gcp-01-5937408f2bba)$ kubectl exec -it pod-1 -- sh error: Internal error occurred: error executing command in container: failed to exec in container: failed to start exec "c00e8be23d1fdc9672d8098d2688e4e3e78039879d6c4dcc5ebe10dc64aa91a9": OCI runtime exec failed: exec failed: unable to start container process: exec: "sh": executable file not found in $PATH: unknown pod1 is broken i was able to continue the task even ping fail hopefully

Thanh N. · Reviewed أكثر من 3 سنوات ago

Ping uses ICMP protocol which isn't port specific, so was not able to run the ping command in Task 3 with a port as ping 10.60.2.5:8080 Neither was I able to run the command kubectl exec -it pod-1 -- sh it worked for pod-2, so just delete pod-1 and changed the image in the yaml to use the same img as pod-2 which got it going

Justin J. · Reviewed أكثر من 3 سنوات ago

Gonzalo L. · Reviewed أكثر من 3 سنوات ago