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

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. · Revisado há almost 4 years

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

sachin m. · Revisado há almost 4 years

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

Taku K. · Revisado há almost 4 years

Taku K. · Revisado há almost 4 years

Piyush R. · Revisado há almost 4 years

Pengkuh D. · Revisado há almost 4 years

Mohan Krishna A. · Revisado há almost 4 years

Basavaraj H. · Revisado há almost 4 years

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. · Revisado há almost 4 years

ALOK K. · Revisado há almost 4 years

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. · Revisado há almost 4 years

Chun-Te S. · Revisado há almost 4 years

Amasidda L. · Revisado há almost 4 years

Mohit B. · Revisado há almost 4 years

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. · Revisado há almost 4 years

Mohan Krishna A. · Revisado há almost 4 years

Pushpanjali S. · Revisado há almost 4 years

Weichen L. · Revisado há almost 4 years

Vignesh R. · Revisado há almost 4 years

Boran L. · Revisado há almost 4 years

Robin S. · Revisado há almost 4 years

Sujnana R. · Revisado há almost 4 years

Vivek B. · Revisado há almost 4 years

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. · Revisado há almost 4 years

Tom P. · Revisado há almost 4 years