Exploring Cost-optimization for GKE Virtual Machines Reviews

ALOK K. · Reviewed about 3 years ago

not properly labs

Muhammad M. · Reviewed about 3 years ago

Muhammad R. · Reviewed about 3 years ago

Sonali P. · Reviewed about 3 years ago

Islam Nurul Y. · Reviewed about 3 years ago

Sofhila W. · Reviewed about 3 years ago

Abhijit S. · Reviewed about 3 years ago

Maryam Khansa' M. · Reviewed about 3 years ago

Rajesh S. · Reviewed about 3 years ago

Mikołaj B. · Reviewed about 3 years ago

---- this command : kubectl exec -it pod-1 -- sh error: Internal error occurred: error executing command in container: failed to exec in container: failed to start exec "f38c78c3e6c294f89063f0a7b6ec02045d38726e9d692b12dc772ecdca7d2ed4": OCI runtime exec failed: exec failed: unable to start container process: exec: "sh": executable file not found in $PATH: unknown

Arief Y. · Reviewed about 3 years ago

Dmytro K. · Reviewed about 3 years ago

oke

gilang j. · Reviewed about 3 years ago

Arief Y. · Reviewed about 3 years ago

Alejandro L. · Reviewed about 3 years ago

Anton P. · Reviewed about 3 years ago

marcel s. · Reviewed over 3 years ago

Can't enter the pod-1. Maybe because the images of the pods are reversed. Fix it, please.

Feuer F. · Reviewed over 3 years ago

Kirubanandam P. · Reviewed over 3 years ago

Pon D. · Reviewed over 3 years ago

some instructions towards the end are outdated and does not work such as: kubectl exec -it pod-1 -- sh pinging pod-2

Yasmin Gabrielle P. · Reviewed over 3 years ago

CAN'T FINISH EXERCISE !! error: Internal error occurred: error executing command in container: failed to exec in container: failed to start exec "6c97ecadcf11b54909af7f5b12a64e5b7f0a5f1f56f91af1f20a65bbe2a544e0": OCI runtime exec failed: exec failed: unable to start container process: exec: "sh": executable file not found in $PATH: unknown

Igor B. · Reviewed over 3 years ago

Sreenivas T. · Reviewed over 3 years ago

Fachriansyah M. · Reviewed over 3 years ago