Esplorazione dell'ottimizzazione dei costi per le macchine virtuali GKE recensioni

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. · Recensione inserita quasi 4 anni fa

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

sachin m. · Recensione inserita quasi 4 anni fa

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

Taku K. · Recensione inserita quasi 4 anni fa

Taku K. · Recensione inserita quasi 4 anni fa

Piyush R. · Recensione inserita quasi 4 anni fa

Pengkuh D. · Recensione inserita quasi 4 anni fa

Mohan Krishna A. · Recensione inserita quasi 4 anni fa

Basavaraj H. · Recensione inserita quasi 4 anni fa

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. · Recensione inserita quasi 4 anni fa

ALOK K. · Recensione inserita quasi 4 anni fa

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. · Recensione inserita quasi 4 anni fa

Chun-Te S. · Recensione inserita quasi 4 anni fa

Amasidda L. · Recensione inserita quasi 4 anni fa

Mohit B. · Recensione inserita quasi 4 anni fa

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. · Recensione inserita quasi 4 anni fa

Mohan Krishna A. · Recensione inserita quasi 4 anni fa

Pushpanjali S. · Recensione inserita quasi 4 anni fa

Weichen L. · Recensione inserita quasi 4 anni fa

Vignesh R. · Recensione inserita quasi 4 anni fa

Boran L. · Recensione inserita quasi 4 anni fa

Robin S. · Recensione inserita quasi 4 anni fa

Sujnana R. · Recensione inserita quasi 4 anni fa

Vivek B. · Recensione inserita quasi 4 anni fa

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. · Recensione inserita quasi 4 anni fa

Tom P. · Recensione inserita quasi 4 anni fa