Working with Artifact Registry Reviews

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

Michael W. · Reviewed 11 ay ago

Raj D. · Reviewed 11 ay ago

Anindya Aryoko C. · Reviewed 11 ay ago

Chaitanya V. · Reviewed 11 ay ago

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

Arthur E. · Reviewed 11 ay ago

Shandy Satria N. · Reviewed 11 ay ago

Anindya Aryoko C. · Reviewed 11 ay ago

Riska Amelia Puspita Sari C. · Reviewed 11 ay ago

Andika D. · Reviewed 11 ay ago

Daffa Febrian Saputr C. · Reviewed 11 ay ago

Ismael C. · Reviewed 11 ay ago

Ismael C. · Reviewed 11 ay ago

Arya S. · Reviewed 11 ay ago

Ismael C. · Reviewed 11 ay ago

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. · Reviewed 11 ay ago

Rafli Arabiansyah C. · Reviewed 11 ay ago

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. · Reviewed 11 ay ago

Maximiliano P. · Reviewed 11 ay ago

T M. · Reviewed 11 ay ago

Akhilesh R. · Reviewed 11 ay ago

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

colton l. · Reviewed 11 ay ago

Violia Ruana Nur'aini Sagita C. · Reviewed 11 ay ago

Kishore Kumar V. · Reviewed 11 ay ago

Violia Ruana Nur'aini Sagita C. · Reviewed 11 ay ago

Santwana P. · Reviewed 11 ay ago