关于“Configuring an HTTP Load Balancer with Google Cloud Armor”的评价

this is most unfair lab and dissapointed with error

Cheong T. · 评论about 5 years之前

Ransford O. · 评论about 5 years之前

Josephat p. · 评论about 5 years之前

Alex T. · 评论about 5 years之前

Great

Nicola B. · 评论about 5 years之前

Priya G. · 评论about 5 years之前

Chun W. · 评论about 5 years之前

Othman K. · 评论about 5 years之前

LTI S. · 评论about 5 years之前

Chua T. · 评论about 5 years之前

LTI S. · 评论about 5 years之前

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. · 评论about 5 years之前

no se carga los pasos ya realizados

PAEZ S. · 评论about 5 years之前

ANTONY NIRMAL RAJ A. · 评论about 5 years之前

Damian C. · 评论about 5 years之前

Jennifer P. · 评论about 5 years之前

Francis Alberto V. · 评论about 5 years之前

Nilesh P. · 评论about 5 years之前

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

Marimuthu P. · 评论about 5 years之前

Rodrigo M. · 评论about 5 years之前

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. · 评论about 5 years之前

Nicholas H. · 评论about 5 years之前

Trony C. · 评论about 5 years之前

Graham R. · 评论about 5 years之前

Chintan S. · 评论about 5 years之前