(NOTE: This is used to report product bugs:
To report a security vulnerability, please visit https://istio.io/about/security-vulnerabilities
To ask questions about how to use Istio, please visit https://discuss.istio.io)

Bug description

Istio.io moved up to a new weekly istio build and two istio.io documentation tests are now failing when timeouts are being set but don't appear to be working.

1. https://istio.io/latest/docs/tasks/traffic-management/egress/egress-control/#manage-traffic-to-external-services
   One sets a timeout in Step Demo walkthrough #2 and expects a failure (504) in step add demos from amalgam8 #3 but gets a 200…

2. https://istio.io/latest/docs/tasks/traffic-management/request-timeouts/#request-timeouts
   In step Initial stab at some governance type of docs #5 of that section, it says that the Reviews section should NOT be shown (as a .5 sec timeout was added). The reviews section still displays so it seems the timeout added in Step Define schema for configs posted to TPR #4 is not working.

[ ] Docs
[ ] Installation
[x] Networking
[ ] Performance and Scalability
[ ] Extensions and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
[ ] Upgrade

Expected behavior

The documentation test should continue to pass as we move up istio.io/istio references

Steps to reproduce the bug

One can look at https://github.com/istio/istio.io/tree/master/tests#running-the-tests to see about running the tests.

Example for a Mac with a kind cluster:
TEST_ENV=kind ADDITIONAL_CONTAINER_OPTIONS="--network host" make doc.test.profile_none TEST=tasks/traffic-management/egress/egress-control/test.sh

Version (include the output of istioctl version --remote and kubectl version --short and helm version --short if you used Helm)

1.10-alpha.ba8228cc703fa11542c3e97c1702688d072152a1

How was Istio installed?

test framework

Environment where the bug was observed (cloud vendor, OS, etc)

test pipeline

Additionally, please consider running istioctl bug-report and attach the generated cluster-state tarball to this issue.
Refer cluster state archive for more details.