关于“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前审核