关于“設定可自動調度資源的應用程式負載平衡器”的评价

Akshitha b. · 评论24 days之前

el capitulo final no esta bien explicado

Rodolfo A. · 评论24 days之前

Rajashekar P. · 评论24 days之前

THARUNI SRI M. · 评论24 days之前

Kirian G. · 评论24 days之前

SIVASANKAR B U. · 评论24 days之前

Yash N. · 评论24 days之前

mahalakshmi R. · 评论24 days之前

Yash N. · 评论24 days之前

Kavi N. · 评论24 days之前

Selvi P. · 评论24 days之前

Arpita P. · 评论24 days之前

good

Pradeep P. · 评论24 days之前

Thirisha K. · 评论24 days之前

Aykun Z. · 评论24 days之前

Hi, I wasn't able to connect to the webserver and stress-test VMs using the standard "SSH" button in the Cloud Console. I ended up having to use Cloud Shell and Gemini to manually troubleshoot and force the connection via gcloud. For your awareness, here are the specific environmental blockers that prevented a standard connection: Incomplete IAP Setup: The IAP API (iap.googleapis.com) was disabled by default. Once enabled, I also had to manually grant my student account the iap.tunnelResourceAccessor role and create a firewall rule to allow TCP:22 ingress from the IAP proxy range (35.235.240.0/20). OS Login Conflict (Major Blocker): Even after fixing IAP and generating fresh SSH keys in Cloud Shell, I hit a persistent Permission denied (publickey) error. The VMs were enforcing OS Login, which rejected my Cloud Shell keys. Adding the osAdminLogin role didn't propagate fast enough, so I had to manually bypass it by applying --metadata="enable-oslogin=FALSE" to both VMs to finally get in. Suggestion: It would be highly beneficial if future iterations of this lab either pre-provisioned the necessary IAP/OS Login IAM roles and firewall rules, or simply disabled OS Login by default on the VMs so the console SSH button works seamlessly. Thanks!

Dumitru T. · 评论24 days之前

HARSHITHA S H G. · 评论24 days之前

Ramanan R. · 评论24 days之前

Dhinesh Kumar A. · 评论24 days之前

Chengqiang L. · 评论24 days之前

Prince G. · 评论24 days之前

Arya Y. · 评论24 days之前

n

Thirumoorthy M. · 评论24 days之前

average

Sigal S. · 评论24 days之前

Ravi T. · 评论24 days之前