Configure an Internal Network Load Balancer Reviews

MUKESHKANNAN M. · Reviewed about 1 year ago

Gavireddy Veera Yasaswini .. · Reviewed about 1 year ago

Arunachalam S. · Reviewed about 1 year ago

Saurabh G. · Reviewed about 1 year ago

Rohith K. · Reviewed about 1 year ago

Luis Geovanni D. · Reviewed about 1 year ago

Simon N. · Reviewed about 1 year ago

Sharath T. · Reviewed about 1 year ago

Микола Д. · Reviewed about 1 year ago

Erick Osvaldo F. · Reviewed about 1 year ago

Sheila J. · Reviewed about 1 year ago

Kumar R. · Reviewed about 1 year ago

Omar S. · Reviewed about 1 year ago

Eric P. · Reviewed about 1 year ago

Gabriel G. · Reviewed about 1 year ago

Keith H. · Reviewed about 1 year ago

Vaishali K. · Reviewed about 1 year ago

Maneesh raj k. · Reviewed about 1 year ago

Vaishali K. · Reviewed about 1 year ago

Cristian V. · Reviewed about 1 year ago

Ming Keat P. · Reviewed about 1 year ago

Ishtiaq S. · Reviewed about 1 year ago

Vemu A. · Reviewed about 1 year ago

Robin A. · Reviewed about 1 year ago

Lab env is not stable: 1. On the first run of the scripts "sudo google_metadata_script_runner startup" on instance-group-1* and instance-group-2* vm script stuck on startup-script: Processing triggers for man-db (2.9.4-2) ... Ctrl-C and re-run of the script helps, but why do we need man pages installed on those hosts? 2. After creating load balancer, linking backends, frontend, creating ip for LB and health-checks, virtual machines in the pool are reset to their default apache webpages. and curl 10.10.30.5 does not report "<h1>Internal Load Balancing Lab</h1>" but the "<title>Index of /</title>" HTML-page. to make LB correctly report - we have to re-run startup scripts on VM. since this part of the LAB does not have automated checks, I assume most users just click "end lab" and do not see that it not works as described

Yuri G. · Reviewed about 1 year ago