Exploring Cost-optimization for GKE Virtual Machines Reviews

Pathetic. Support is worst.

Pradip G. · Reviewed about 3 years ago

cant get shell access on pod 1.

Vipul C. · Reviewed about 3 years ago

Vipul C. · Reviewed about 3 years ago

Amanda L. · Reviewed over 3 years ago

Kelvin L. · Reviewed over 3 years ago

Nada O. · Reviewed over 3 years ago

Amr H. · Reviewed over 3 years ago

Ahmed N. · Reviewed over 3 years ago

Abdul Rahman M. · Reviewed over 3 years ago

Brian R. · Reviewed over 3 years ago

Ablaye F. · Reviewed over 3 years ago

Ghada a. · Reviewed over 3 years ago

so fuc*ing slow when creating cluster

Arif P. · Reviewed over 3 years ago

Arif P. · Reviewed over 3 years ago

Arun B. · Reviewed over 3 years ago

Brandon C. · Reviewed over 3 years ago

Aben Liangliang L. · Reviewed over 3 years ago

Chengjie F. · Reviewed over 3 years ago

Zhen L. · Reviewed over 3 years ago

Rayane B. · Reviewed over 3 years ago

The ping command did not work - so not traffic flow logs generated and did not see the data to put into BigQuery. Error : student_00_309e927e62bd@cloudshell:/ (qwiklabs-gcp-03-2389d82927e7)$ kubectl exec -it pod-1 -- sh error: Internal error occurred: error executing command in container: failed to exec in container: failed to start exec "91d7a216cbdd72d58d77faded47940c5a20b9ef60381b1a25263e1f600c61d9e": OCI runtime exec failed: exec failed: unable to start container process: exec: "sh": executable file not found in $PATH: unknown I had lots of problems during this lab - I have tried it twice.

Sunny L. · Reviewed over 3 years ago

Tomek J. · Reviewed over 3 years ago

running sh on the pod does not work

Lautaro Alejandro B. · Reviewed over 3 years ago

Ablaye F. · Reviewed over 3 years ago

pod1 uses distroless, so it no longer has `sh`, the format for `ping` does not include the port, so `:8080` is just confusing, does not work.

Gabor B. · Reviewed over 3 years ago