Configurar um balanceador de carga de rede interno avaliações

Jason L. · Revisado há 3 days

Pavlo K. · Revisado há 3 days

JIGYASA T. · Revisado há 3 days

Shubhangi-A Y. · Revisado há 3 days

Akash A. · Revisado há 3 days

Saverio C. · Revisado há 3 days

Muhilan V. · Revisado há 3 days

1cca240 R. · Revisado há 3 days

Abdoulaye S. · Revisado há 3 days

PHILEMON MANUEL S. · Revisado há 3 days

Konna L. · Revisado há 3 days

Pablo T. · Revisado há 3 days

Very poor lab. Because initially it didnt allow me access to lab saying that previous lab was closed incorrectly.

Bharadwaj S. · Revisado há 3 days

Fiodar R. · Revisado há 3 days

B V. · Revisado há 3 days

Abdullah S. · Revisado há 3 days

ssh not work , please look on it

Jayant K. · Revisado há 3 days

Jayant K. · Revisado há 3 days

ESWAR V. · Revisado há 3 days

End Lab Button is difficult to find

Noor R. · Revisado há 3 days

A DINESH NARAYANA S. · Revisado há 3 days

Rohan K. · Revisado há 3 days

ANDRES FELIPE D. · Revisado há 3 days

Great lab, well guided and set up!

Enrique R. · Revisado há 3 days

I encountered an issue while trying to SSH into the VM (instance-group-1-5jft) using IAP. The connection kept failing with a generic VPC/IAP configuration error. After troubleshooting, I discovered that OS Login was enabled by default on the project/instance, which blocked the standard SSH key connection with the provided student credentials. I managed to fix it and complete the lab by manually disabling OS Login via Cloud Shell: gcloud compute instances add-metadata instance-group-1-5jft --zone="asia-south1-c" --metadata="enable-oslogin=FALSE" Suggestion: Please explicitly disable OS Login on the instances during the deployment phase so other students don't get stuck.

Fernando A. · Revisado há 3 days