关于“开发 Google Cloud 网络：实验室挑战赛”的评价

Andreas L. · 已于 almost 3 years前审核

Mita M. · 已于 almost 3 years前审核

Laurens E. · 已于 almost 3 years前审核

Alifian Aji Adiaksa C. · 已于 almost 3 years前审核

Suresh Mathav P. · 已于 almost 3 years前审核

Hasan A. · 已于 almost 3 years前审核

Suresh Mathav P. · 已于 almost 3 years前审核

Gas udah aman

Feri Y. · 已于 almost 3 years前审核

Emmanuel N. · 已于 almost 3 years前审核

Emmanuel N. · 已于 almost 3 years前审核

Sambit Kumar S. · 已于 almost 3 years前审核

Vikash P. · 已于 almost 3 years前审核

Tushar R. · 已于 almost 3 years前审核

Konstantinos P. · 已于 almost 3 years前审核

Surabhi A. · 已于 almost 3 years前审核

Sajid Fardan Nuazhar C. · 已于 almost 3 years前审核

Alberto C. · 已于 almost 3 years前审核

Jedrzej P. · 已于 almost 3 years前审核

Ramdhan S. · 已于 almost 3 years前审核

First time: * Bugged "No subnetworks in this region" for the VMs while the resources are in correct region (verified multiple time... maybe I missed it but...), I tried recreated the impacted vpc (prod) but once deleted still displayed as "Already in use" => have to retry the lab from start. Second time: * Policy in lab always been: "not specified, use the default setting of configuration", except that here the default setting for Cloud SQL Mysql is Enterprise Plus => Forced Shutdown the lab due to "overcost" => Should be precised the target env 'Enterprise' and expected env size, ex: dev Third time: * Timeout due to not seen the option for deactivating the "automanaged" kubernetes option at first and clicking create by mistake => 1h is quite short when the k8s provision and the cloudsql takes each 15m to be created (45m lost for resources creation). Fourth time: * Did all resources creations in parallel ended up with 20 min lefts

Mathieu M. · 已于 almost 3 years前审核

Resa N. · 已于 almost 3 years前审核

Ashutosh J. · 已于 almost 3 years前审核

Swati A. · 已于 almost 3 years前审核

Bayu Rizkhi Dwi Saputra C. · 已于 almost 3 years前审核

Atharva B. · 已于 almost 3 years前审核