Exploring Cost-optimization for GKE Virtual Machines avis

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. · Examiné il y a environ 3 ans

Desmond F. · Examiné il y a environ 3 ans

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

Normala A. · Examiné il y a environ 3 ans

Isaac G. · Examiné il y a environ 3 ans

Last task Not Working, can't detect progress!

Normala A. · Examiné il y a environ 3 ans

Jeremy L. · Examiné il y a environ 3 ans

Damian K. · Examiné il y a environ 3 ans

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. · Examiné il y a environ 3 ans

Andrés S. · Examiné il y a environ 3 ans

Stanley P. · Examiné il y a environ 3 ans

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

Dinkar G. · Examiné il y a environ 3 ans

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

haeyoon J. · Examiné il y a environ 3 ans

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

haeyoon J. · Examiné il y a environ 3 ans

Anjaneyulu B. · Examiné il y a environ 3 ans

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

Matt G. · Examiné il y a environ 3 ans

Archit S. · Examiné il y a environ 3 ans

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

Dinkar G. · Examiné il y a environ 3 ans

Turky A. · Examiné il y a environ 3 ans

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. · Examiné il y a environ 3 ans

帅 刘. · Examiné il y a environ 3 ans

Link L. · Examiné il y a environ 3 ans

cant get shell access on pod 1.

Vipul C. · Examiné il y a environ 3 ans

last checkmark didn't work

Matt G. · Examiné il y a environ 3 ans

Nishandhini A. · Examiné il y a environ 3 ans

Nimith J. · Examiné il y a environ 3 ans