Working with Artifact Registry avis

Luthfi M. · Examiné il y a 11 mois

after few trials it worked with cloud code. But nevertheless it is very slow.

Michael W. · Examiné il y a 11 mois

Raj D. · Examiné il y a 11 mois

Anindya Aryoko C. · Examiné il y a 11 mois

Chaitanya V. · Examiné il y a 11 mois

Kubernetes and Compute Engine in the Cloud Shell Editor were really slow.

Arthur E. · Examiné il y a 11 mois

Shandy Satria N. · Examiné il y a 11 mois

Anindya Aryoko C. · Examiné il y a 11 mois

Riska Amelia Puspita Sari C. · Examiné il y a 11 mois

Andika D. · Examiné il y a 11 mois

Daffa Febrian Saputr C. · Examiné il y a 11 mois

Ismael C. · Examiné il y a 11 mois

Ismael C. · Examiné il y a 11 mois

Arya S. · Examiné il y a 11 mois

Ismael C. · Examiné il y a 11 mois

I waited a long time just to wait for an error due to a lack of resources in creating the cluster and I couldn't complete task 1 and waited more than 40 minutes.

Arya S. · Examiné il y a 11 mois

Rafli Arabiansyah C. · Examiné il y a 11 mois

It took 10m for GKE to init, and Cloud Code was horrifyingly slow to load. The time spent in Cloud Code was excessive compared to the time actively learning about artifact registry, so the lab title is a little misleading.

Christopher A. · Examiné il y a 11 mois

Maximiliano P. · Examiné il y a 11 mois

T M. · Examiné il y a 11 mois

Akhilesh R. · Examiné il y a 11 mois

cloud shell editor ran so slow the lab couldn't be finished on time

colton l. · Examiné il y a 11 mois

Violia Ruana Nur'aini Sagita C. · Examiné il y a 11 mois

Kishore Kumar V. · Examiné il y a 11 mois

Violia Ruana Nur'aini Sagita C. · Examiné il y a 11 mois