Como explorar a otimização de custos para máquinas virtuais do GKE avaliações

SERHII D. · Revisado há over 3 years

Zhandy Z. · Revisado há over 3 years

Neftali Enrique . · Revisado há over 3 years

Bhaskar G. · Revisado há over 3 years

Mostafa R. · Revisado há over 3 years

Nobel T. · Revisado há over 3 years

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

Zsolt T. · Revisado há over 3 years

Gonçalo C. · Revisado há over 3 years

Olga P. · Revisado há over 3 years

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. · Revisado há over 3 years

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. · Revisado há over 3 years

Gonzalo L. · Revisado há over 3 years

Nadhiful F. · Revisado há over 3 years

Hapid R. · Revisado há over 3 years

Aldycky Bagus W. · Revisado há over 3 years

Gonçalo C. · Revisado há over 3 years

Denys L. · Revisado há over 3 years

Abdrhman A. · Revisado há over 3 years

Vladyslav H. · Revisado há over 3 years

John M. · Revisado há over 3 years

Muhammad Farras R. · Revisado há over 3 years

Kei K. · Revisado há over 3 years

Haolin Z. · Revisado há over 3 years

Jorge M. · Revisado há over 3 years

Jessica A. · Revisado há over 3 years