Working with Artifact Registry Reviews

Muvidha Fatmawati Putri C. · Reviewed about 1 year ago

Luthfi M. · Reviewed about 1 year ago

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

Michael W. · Reviewed about 1 year ago

Raj D. · Reviewed about 1 year ago

Anindya Aryoko C. · Reviewed about 1 year ago

Chaitanya V. · Reviewed about 1 year ago

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

Arthur E. · Reviewed about 1 year ago

Shandy Satria N. · Reviewed about 1 year ago

Anindya Aryoko C. · Reviewed about 1 year ago

Riska Amelia Puspita Sari C. · Reviewed about 1 year ago

Andika D. · Reviewed about 1 year ago

Daffa Febrian Saputr C. · Reviewed about 1 year ago

Ismael C. · Reviewed about 1 year ago

Ismael C. · Reviewed about 1 year ago

Arya S. · Reviewed about 1 year ago

Ismael C. · Reviewed about 1 year 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 about 1 year ago

Rafli Arabiansyah C. · Reviewed about 1 year 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 about 1 year ago

Maximiliano P. · Reviewed about 1 year ago

T M. · Reviewed about 1 year ago

Akhilesh R. · Reviewed about 1 year ago

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

colton l. · Reviewed about 1 year ago

Violia Ruana Nur'aini Sagita C. · Reviewed about 1 year ago

Kishore Kumar V. · Reviewed about 1 year ago