Opinie (Exploring Cost-optimization for GKE Virtual Machines)

Robin S. · Sprawdzono ponad 3 lata temu

Sujnana R. · Sprawdzono ponad 3 lata temu

Vivek B. · Sprawdzono ponad 3 lata temu

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. · Sprawdzono ponad 3 lata temu

Tom P. · Sprawdzono ponad 3 lata temu

P N V KRISHNA T. · Sprawdzono ponad 3 lata temu

There is an issue in GCP side. hence not able to complete this lab

ramesh b. · Sprawdzono ponad 3 lata temu

Willie S. · Sprawdzono ponad 3 lata temu

in the task3 environment is not working such as shell is not opening for pod1

ALOK K. · Sprawdzono ponad 3 lata temu

Cannot exec into pod-1, it doesn't have sh and to run ping on pod-2, and last check keeps failing at sink creation, even y retried to create it multiple times. And I think that "ping ip:port" is not supported, you need another tool for that.

Federico T. · Sprawdzono ponad 3 lata temu

abdulhameed a. · Sprawdzono ponad 3 lata temu

Andrés R. T. · Sprawdzono ponad 3 lata temu

Shivanshu D. · Sprawdzono ponad 3 lata temu

failed to exec in container: failed to start exec OCI runtime exec failed: exec failed: unable to start container process: exec: "ping": executable file not found in $PATH: unknow

Carlos Felipe M. · Sprawdzono ponad 3 lata temu

Sivamanikanta G. · Sprawdzono ponad 3 lata temu

Rohan M. · Sprawdzono ponad 3 lata temu

ANIL MANOHAR M. · Sprawdzono ponad 3 lata temu

Cesar B. · Sprawdzono ponad 3 lata temu

Mathias D. · Sprawdzono ponad 3 lata temu

Rosario C. · Sprawdzono ponad 3 lata temu

Mathias D. · Sprawdzono ponad 3 lata temu

kubectl exec -it pod-1 -- sh. "This command do not work"

Satish B. · Sprawdzono ponad 3 lata temu

Cannot exec into pod-1, it doesn't have sh and to run ping on pod-2, and last check keeps failing at sink creation, even y retried to create it multiple times. And I think that "ping ip:port" is not supported, you need another tool for that.

Federico T. · Sprawdzono ponad 3 lata temu

Mathias D. · Sprawdzono ponad 3 lata temu

Nimith J. · Sprawdzono ponad 3 lata temu