Configuring an HTTP Load Balancer with Google Cloud Armor Reviews

Maurizio C. · Reviewed أكثر من 5 سنوات ago

this is most unfair lab and dissapointed with error

Cheong T. · Reviewed أكثر من 5 سنوات ago

Ransford O. · Reviewed أكثر من 5 سنوات ago

Josephat p. · Reviewed أكثر من 5 سنوات ago

Alex T. · Reviewed أكثر من 5 سنوات ago

Great

Nicola B. · Reviewed أكثر من 5 سنوات ago

Priya G. · Reviewed أكثر من 5 سنوات ago

Chun W. · Reviewed أكثر من 5 سنوات ago

Othman K. · Reviewed أكثر من 5 سنوات ago

LTI S. · Reviewed أكثر من 5 سنوات ago

Chua T. · Reviewed أكثر من 5 سنوات ago

LTI S. · Reviewed أكثر من 5 سنوات ago

a few tricky bits. Needed to ssh via cloudshell, also took more than a few minutes for LB to healthcheck, and cloud armour rules to kick in.

Sam Y. · Reviewed أكثر من 5 سنوات ago

no se carga los pasos ya realizados

PAEZ S. · Reviewed أكثر من 5 سنوات ago

ANTONY NIRMAL RAJ A. · Reviewed أكثر من 5 سنوات ago

Damian C. · Reviewed أكثر من 5 سنوات ago

Jennifer P. · Reviewed أكثر من 5 سنوات ago

Francis Alberto V. · Reviewed أكثر من 5 سنوات ago

Nilesh P. · Reviewed أكثر من 5 سنوات ago

Step 3, for europe-west1, shall have instructions to create metadat with startup scripts and network tag

Marimuthu P. · Reviewed أكثر من 5 سنوات ago

Rodrigo M. · Reviewed أكثر من 5 سنوات ago

great concept but the set up has the siege-vm address change with every request as it hits the load balancer. so the cloud armor rule to block the request is meaningless. Also the load probably with the ip shifting did not push the instance above 10%. there as a huge throttle in place on siege as well. i stopped going into to configure that, considered ab but that's just overkill - i think the set up of the lab needs to be narrowed to trigger the load and blocks -- conceptually i know what i was meant to see - but this lab really doesn't get there currently - revisit with current state of GCP - maybe some defaults have changed -- i could have missed something -- double checked all the names ..

Joshua L. · Reviewed أكثر من 5 سنوات ago

Nicholas H. · Reviewed أكثر من 5 سنوات ago

Trony C. · Reviewed أكثر من 5 سنوات ago

Graham R. · Reviewed أكثر من 5 سنوات ago