Signed-off-by: Piotr Sikora <piotrsikora@google.com>

…yproxy#162)

Backport envoyproxy/envoy-wasm#422 and its prerequisite (envoyproxy#10009).

* Plumb the flaky flag from envoy_cc_test to the native.cc_test (envoyproxy#10009)

Signed-off-by: Yan Avlasov <yavlasov@google.com>

* ci: mark //test/integration:protocol_integration_test as flaky. (envoyproxy#422)

Signed-off-by: Piotr Sikora <piotrsikora@google.com>

zh-translation: docs/root/intro/arch_overview/operations/init.rst

Using `0.0.0.0` when connecting over a socket to Envoy doesn't work when building to a physical device even though it works fine on a simulator.

To fix this, we can use `localhost` and disable ATS for the demos.

As a long term fix, there are a few options, but the foremost/preferred is to call directly into Envoy over request interfaces instead of using a local socket. See [this section](https://docs.google.com/document/d/1eLbJEXog2Rn7wTBEbDIjpDV7dHecV_DV_dw8P5ZgbL4/edit#heading=h.nx6ynimf9ztp) for more details on this, slated for v0.2.

Discussion: https://envoyproxy.slack.com/archives/CKQ2LK23G/p1561146122069800

Signed-off-by: Michael Rebello <mrebello@lyft.com>
Signed-off-by: JP Simard <jp@jpsim.com>

Using `0.0.0.0` when connecting over a socket to Envoy doesn't work when building to a physical device even though it works fine on a simulator.

To fix this, we can use `localhost` and disable ATS for the demos.

As a long term fix, there are a few options, but the foremost/preferred is to call directly into Envoy over request interfaces instead of using a local socket. See [this section](https://docs.google.com/document/d/1eLbJEXog2Rn7wTBEbDIjpDV7dHecV_DV_dw8P5ZgbL4/edit#heading=h.nx6ynimf9ztp) for more details on this, slated for v0.2.

Discussion: https://envoyproxy.slack.com/archives/CKQ2LK23G/p1561146122069800

Signed-off-by: Michael Rebello <mrebello@lyft.com>
Signed-off-by: JP Simard <jp@jpsim.com>