Exploring Cost-optimization for GKE Virtual Machines Reviews

SERHII D. · Reviewed over 3 years ago

Zhandy Z. · Reviewed over 3 years ago

Neftali Enrique . · Reviewed over 3 years ago

Bhaskar G. · Reviewed over 3 years ago

Mostafa R. · Reviewed over 3 years ago

Nobel T. · Reviewed over 3 years ago

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

Zsolt T. · Reviewed over 3 years ago

Gonçalo C. · Reviewed over 3 years ago

Olga P. · Reviewed over 3 years 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 over 3 years 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 over 3 years ago

Gonzalo L. · Reviewed over 3 years ago

Nadhiful F. · Reviewed over 3 years ago

Hapid R. · Reviewed over 3 years ago

Aldycky Bagus W. · Reviewed over 3 years ago

Gonçalo C. · Reviewed over 3 years ago

Denys L. · Reviewed over 3 years ago

Abdrhman A. · Reviewed over 3 years ago

Vladyslav H. · Reviewed over 3 years ago

John M. · Reviewed over 3 years ago

Muhammad Farras R. · Reviewed over 3 years ago

Kei K. · Reviewed over 3 years ago

Haolin Z. · Reviewed over 3 years ago

Jorge M. · Reviewed over 3 years ago

Jessica A. · Reviewed over 3 years ago