Working with Artifact Registry Reviews

Cluster creation takes forever and hindering with lab completion

Sainarasimhan K. · Reviewed about 1 month ago

I Gusti Bagus Putrawan C. · Reviewed about 1 month ago

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

sri C. · Reviewed about 1 month ago

Oleksii G. · Reviewed about 1 month ago

Muvidha Fatmawati Putri C. · Reviewed about 1 month ago

Luthfi Mubarok C. · Reviewed about 1 month ago

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

Michael W. · Reviewed about 1 month ago

Raj D. · Reviewed about 1 month ago

Anindya Aryoko C. · Reviewed about 1 month ago

Chaitanya V. · Reviewed about 1 month ago

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

Arthur E. · Reviewed about 1 month ago

Shandy Satria Nugraha C. · Reviewed about 1 month ago

Anindya Aryoko C. · Reviewed about 1 month ago

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

Andika D. · Reviewed about 1 month ago

Daffa Febrian Saputr C. · Reviewed about 1 month ago

Ismael C. · Reviewed about 1 month ago

Ismael C. · Reviewed about 1 month ago

Arya Saputra C. · Reviewed about 1 month ago

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

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

Maximiliano P. · Reviewed about 1 month ago