Exploring Cost-optimization for GKE Virtual Machines Reviews

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

Nadhiful F. · Reviewed больше 3 лет ago

Hapid R. · Reviewed больше 3 лет ago

Aldycky Bagus W. · Reviewed больше 3 лет ago

Gonçalo C. · Reviewed больше 3 лет ago

Denys L. · Reviewed больше 3 лет ago

Abdrhman A. · Reviewed больше 3 лет ago

Vladyslav H. · Reviewed больше 3 лет ago

John M. · Reviewed больше 3 лет ago

Muhammad Farras R. · Reviewed больше 3 лет ago

Kei K. · Reviewed больше 3 лет ago

Haolin Z. · Reviewed больше 3 лет ago

Jorge M. · Reviewed больше 3 лет ago

Jessica A. · Reviewed больше 3 лет ago