Working with Artifact Registry Reviews

I Gusti Bagus Putrawan C. · Reviewed over 1 year ago

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

sri C. · Reviewed over 1 year ago

Oleksii G. · Reviewed over 1 year ago

Muvidha Fatmawati Putri C. · Reviewed over 1 year ago

Luthfi M. · Reviewed over 1 year ago

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

Michael W. · Reviewed over 1 year ago

Raj D. · Reviewed over 1 year ago

Anindya Aryoko C. · Reviewed over 1 year ago

Chaitanya V. · Reviewed over 1 year ago

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

Arthur E. · Reviewed over 1 year ago

Shandy Satria N. · Reviewed over 1 year ago

Anindya Aryoko C. · Reviewed over 1 year ago

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

Andika D. · Reviewed over 1 year ago

Daffa Febrian Saputr C. · Reviewed over 1 year ago

Ismael C. · Reviewed over 1 year ago

Ismael C. · Reviewed over 1 year ago

Arya S. · Reviewed over 1 year ago

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

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

Maximiliano P. · Reviewed over 1 year ago

T M. · Reviewed over 1 year ago