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

couldn't progress beyond creating pod-1 (Step 3).. even when pod-1 AND pod-2 were created from the manifest. Extremely frustrating to waste my time like this.

JR C. · Revisado há about 3 years

Desmond F. · Revisado há about 3 years

Second try. Last task Not Working, can't detect progress! and can't Edit Flow Logs in VPC Network

Normala A. · Revisado há about 3 years

Isaac G. · Revisado há about 3 years

Last task Not Working, can't detect progress!

Normala A. · Revisado há about 3 years

Jeremy L. · Revisado há about 3 years

Damian K. · Revisado há about 3 years

lab has a known bug within Task #3, even when I provide an evidence that I do it right support do not accept it, but reply traditionally we are working on fixing a bug. Traditional bla-bla-bla, no real help. Do, not recommend this lab.

Pavel T. · Revisado há about 3 years

Andrés S. · Revisado há about 3 years

Stanley P. · Revisado há about 3 years

The account was disabled for some reason. Can you please enable my account. Thanks.

Dinkar G. · Revisado há about 3 years

some commands are not working as deprecated so its hard to understan

haeyoon J. · Revisado há about 3 years

some commands are not working as deprecated so its hard to understand what to do

haeyoon J. · Revisado há about 3 years

Anjaneyulu B. · Revisado há about 3 years

last checkmark didn't work; also the image for pod-1 is incorrect

Matt G. · Revisado há about 3 years

Archit S. · Revisado há about 3 years

Pod-2 is in pending state even after a couple of delete pod requests. I will need to start over again. Thanks.

Dinkar G. · Revisado há about 3 years

Turky A. · Revisado há about 3 years

I am get an error that stops me from continuing : 1 - the ecexuted command : kubectl exec -it pod-1 -- sh 2 - the result error : error: Internal error occurred: error executing command in container: failed to exec in container: failed to start exec "2dce4ec8034114f18866f030c778b000c5c647623c7b3a0aa477ef0f9947e3f9": OCI runtime exec failed: exec failed: unable to start container process: exec: "sh": executable file not found in $PATH: unknown

Rachid O. · Revisado há about 3 years

帅 刘. · Revisado há about 3 years

Link L. · Revisado há about 3 years

cant get shell access on pod 1.

Vipul C. · Revisado há about 3 years

last checkmark didn't work

Matt G. · Revisado há about 3 years

Nishandhini A. · Revisado há about 3 years

Nimith J. · Revisado há about 3 years