GKE 仮想マシンの費用最適化について学習する のレビュー

Dwi Septiandi Pengkuh · 約3年前にレビュー済み

Angani Mohan Krishna · 約3年前にレビュー済み

Halasur Basavaraj · 約3年前にレビュー済み

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%.

Nikhar Bhushan · 約3年前にレビュー済み

KUMAR ALOK · 約3年前にレビュー済み

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

Ahl Brenden · 約3年前にレビュー済み

Sung Chun-Te · 約3年前にレビュー済み

Lawar Amasidda · 約3年前にレビュー済み

Beni Mohit · 約3年前にレビュー済み

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.

Nikhar Bhushan · 約3年前にレビュー済み

Angani Mohan Krishna · 約3年前にレビュー済み

Sahu Pushpanjali · 約3年前にレビュー済み

Lai Weichen · 約3年前にレビュー済み

Rajendran Vignesh · 約3年前にレビュー済み

Lee Boran · 約3年前にレビュー済み

Song Robin · 約3年前にレビュー済み

Rai Sujnana · 約3年前にレビュー済み

Balodi Vivek · 約3年前にレビュー済み

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

Arnóczki István · 約3年前にレビュー済み

Petrella Tom · 約3年前にレビュー済み

TEJA P N V KRISHNA · 約3年前にレビュー済み

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

balasubramanian ramesh · 約3年前にレビュー済み

Shen Willie · 約3年前にレビュー済み

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

KUMAR ALOK · 約3年前にレビュー済み

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.

Trasande Federico · 約3年前にレビュー済み