Merge attempt to upstream/36cf26b9d6ac32f5671c24b92f9ea22ab70bc6c1 #1

Description: Use smaller image, bazel 0.28.1, regenerates config with gcc and libcxx Risk Level: Low Testing: CI Docs Changes: Release Notes: Signed-off-by: Lizan Zhou <lizan@tetrate.io>

Add flag when open file (envoyproxy#7445) Signed-off-by: cwsong <cwsong@iflytek.com>

) Signed-off-by: Lizan Zhou <lizan@tetrate.io>

The example shows the request_headers_to_add in the RouteAction, and this should be in the Route Signed-off-by: Christian Ladrón de Guevara Reyes <christian@datank.ai>

This fixes envoyproxy#7357 on windows Visual Studio 2017 Signed-off-by: William Rowe <wrowe@pivotal.io>

Signed-off-by: Asra Ali <asraa@google.com>

Signed-off-by: Derek Argueta <dereka@pinterest.com>

This adds support for parsing server responses and watch events. One or more follow-up PRs will add support for latency measurements and access log. Signed-off-by: Raul Gutierrez Segales <rgs@pinterest.com>

Signed-off-by: Harvey Tuch <htuch@google.com>

Description: Fixes post submit issue from envoyproxy#7786 Risk Level: Testing: Docs Changes: Release Notes: Signed-off-by: Lizan Zhou <lizan@tetrate.io>

…oxy#7427) Signed-off-by: Rama Chavali <rama.rao@salesforce.com>

Make it easier to grok. Signed-off-by: Raul Gutierrez Segales <rgs@pinterest.com>

Signed-off-by: Derek Argueta <dereka@pinterest.com>

Remove an unnecessary bullet list to make the link to the v2 API reference inlined. Signed-off-by: Tal Nordan <github@talnordan.com>

Signed-off-by: Lizan Zhou <lizan@tetrate.io>

Signed-off-by: Derek Argueta <darguetap@gmail.com>

Let the config override the Stackdriver address. This can be used for proxying and testing. Signed-off-by: Emil Mikulic <g-easy@users.noreply.github.com>

…7755) Signed-off-by: Ruslan Nigmatullin <elessar@dropbox.com>

…roxy#7801) Signed-off-by: Yang Song <yasong@google.com>

…roxy#7796) For the first point in envoyproxy#7771 for converting arbitrary protobuf value from header to metadata. Risk Level: Low Testing: Unit tests Docs Changes: Updated version_history.rst Release Notes: Updated version_history.rst Signed-off-by: Yangmin Zhu <ymzhu@google.com>

Signed-off-by: Rama Chavali <rama.rao@salesforce.com>

Use default DNS refresh TTL when DNS returns an NXDOMAIN Risk Level: Medium Testing: unit test, manual test Docs Changes: N/A Release Notes: N/A Fixes #Issue: envoyproxy#7808 Signed-off-by: Yan Xue <yxyan@google.com>

Signed-off-by: Harvey Tuch <htuch@google.com>

revival of envoyproxy#7823 this fixes a particular exception case where an end-user configures a socket address to point at: `https://google.com` instead of just the hostname: `google.com`. instead of throwing an (stoi) error. because it can't turn: `//google.com` into a port. we now through a slightly more sane: `malformed url`. it isn't as good as a protoc-gen-validate message since it's not clear why: `tcp://` gets prepended, but I think it's digestable enough to know, you shouldn't be putting https there. not to mention it is a step forward from: `stoi`. Risk Level: Low Testing: Not only are there unit tests, but you can run through the following configurations and see the new error messages. Docs Changes: None Release Notes: None Signed-off-by: Cynthia Coan <ccoan@instructure.com>

Signed-off-by: Wayne Zhang <qiwzhang@google.com>

Signed-off-by: Mike Schore <mike.schore@gmail.com>

Signed-off-by: Yang Song <yasong@google.com>

Signed-off-by: Auni Ahsan <auni@google.com>

Signed-off-by: Lizan Zhou <lizan@tetrate.io>

Signed-off-by: Derek Argueta <dereka@pinterest.com>

This makes a new config "asan-fuzzer" that links to the libfuzzer engine. To run a fuzz target with asan and libfuzzer, do bazel build --config=asan-fuzzer test/common/router:route_fuzz_test_driver --config=asan-fuzzer bazel-bin/test/common/router/route_fuzz_test_driver test/common/router/route_corpus -runs=-1 (-runs=-1 for indefinite runs, -runs=100 for bounded). Testing: works locally Risk: Low Signed-off-by: Asra Ali <asraa@google.com>

…envoyproxy#7843) Signed-off-by: Henry Yang <hyang@lyft.com>

Signed-off-by: Ruslan Nigmatullin <elessar@dropbox.com>

Signed-off-by: Bence Béky <bnc@google.com>

Signed-off-by: Tony Allen <tallen@lyft.com>

* Convert a few more counter() references to use the StatName interface. Signed-off-by: Joshua Marantz <jmarantz@google.com>

Signed-off-by: Gabriel <gsagula@gmail.com>

Signed-off-by: Gabriel Linden Sagula <gsagula@gmail.com>

Signed-off-by: Bence Béky <bnc@google.com>

Signed-off-by: Jarno Rajahalme <jarno@covalent.io>

Without this change, the default system compiler is used in some rules (e.g. genrules). Signed-off-by: Piotr Sikora <piotrsikora@google.com>

Signed-off-by: Scott LaVigne <lavignes@amazon.com>

Signed-off-by: Bence Béky <bnc@google.com>

Limit the number of outbound (these, waiting to be written into the socket) HTTP/2 frames. When the limit is exceeded the connection is terminated. This mitigates flood exploits where a client continually sends frames that are not subject to flow control without reading server responses. Fixes CVE-2019-9512, CVE-2019-9514 and CVE-2019-9515. Signed-off-by: Yan Avlasov <yavlasov@google.com>

This change adds protections against flooding using PRIORITY and/or WINDOW_UPDATE frames, as well as frames with an empty payload and no end stream flag. Fixes CVE-2019-9511, CVE-2019-9513 and CVE-2019-9518. Signed-off-by: Piotr Sikora <piotrsikora@google.com>

Fixes CVE-2019-9516. Signed-off-by: Piotr Sikora <piotrsikora@google.com>

…Delay (envoyproxy#16) Signed-off-by: Yan Avlasov <yavlasov@google.com>

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

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

…yproxy#26) This is a precursor to envoyproxy#7601 just to land the API change more quickly and make sure it sticks. Risk Level: Low Testing: existing unit tests Docs Changes: n/a Release Notes: n/a Signed-off-by: Alyssa Wilk <alyssar@chromium.org> Signed-off-by: Piotr Sikora <piotrsikora@google.com>

…y#7695) (envoyproxy#27) Making runtime accessible for non-worker threads, and using the new accessor for runtime features. This allows the work done in envoyproxy#7601, moving the strict HTTP checks out of the HCM and into the codec, where the integration tests use them from client/server threads, and other downstream Envoys might use them from non-worker threads as well. Risk Level: High (affects runtime access for all runtime features) Testing: new unit tests, integration tests use in envoyproxy#7601 Docs Changes: n/a Release Notes: n/a Signed-off-by: Alyssa Wilk <alyssar@chromium.org> Signed-off-by: Piotr Sikora <piotrsikora@google.com>

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

…#7885) Signed-off-by: Ruslan Nigmatullin <elessar@dropbox.com>

…yproxy#7859) Description: Add an option to continue on listener filters timeout. Risk Level: Med (mostly guarded by config) Testing: unittest Docs Changes: Added Release Notes: Added Fixes envoyproxy#7195 Signed-off-by: Lizan Zhou <lizan@tetrate.io>

…nvoyproxy#7889) Signed-off-by: Michael Rebello <me@michaelrebello.com>

Signed-off-by: Matt Klein <mklein@lyft.com> Signed-off-by: Piotr Sikora <piotrsikora@google.com>

…xy#7897) This resolves compile line length issues by triggering a command args file bazelbuild/bazel#5163 Signed-off-by: William Rowe <wrowe@pivotal.io>

Signed-off-by: Guangming Wang <guangming.wang@daocloud.io>

Signed-off-by: Alex Konradi <akonradi@google.com>

Signed-off-by: Asra Ali <asraa@google.com>

…y#7886) Signed-off-by: Asra Ali <asraa@google.com>

Signed-off-by: Asra Ali <asraa@google.com>

Signed-off-by: Emil Mikulic <g-easy@users.noreply.github.com>

This change adds histograms for each opcode, e.g.: * getdata * setdata * ... Signed-off-by: Raul Gutierrez Segales <rgs@pinterest.com>

This warms when building: > envoy/api/v2/cluster/filter.proto:12:1: warning: Import google/protobuf/struct.proto but not used. Signed-off-by: Michael Rebello <me@michaelrebello.com>

Limit the number of outbound (these, waiting to be written into the socket) HTTP/2 frames. When the limit is exceeded the connection is terminated. This mitigates flood exploits where a client continually sends frames that are not subject to flow control without reading server responses. Fixes CVE-2019-9512, CVE-2019-9514 and CVE-2019-9515. Signed-off-by: Yan Avlasov <yavlasov@google.com>

This change adds protections against flooding using PRIORITY and/or WINDOW_UPDATE frames, as well as frames with an empty payload and no end stream flag. Fixes CVE-2019-9511, CVE-2019-9513 and CVE-2019-9518. Signed-off-by: Piotr Sikora <piotrsikora@google.com>

Fixes CVE-2019-9516. Signed-off-by: Piotr Sikora <piotrsikora@google.com>

…lushWriteAndDelay (envoyproxy#28) Signed-off-by: Yan Avlasov <yavlasov@google.com>

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

…voyproxy#34) Signed-off-by: Matt Klein <mklein@lyft.com>

…ective chains (envoyproxy#7779) An (no longer annoyingly one-off) solution to the common problem folks run into with Envoy configs where they add their filters behind the router filter and don't get why things aren't working. Ditto for HCM, tcp_proxy etc for L4 Risk Level: Low (except for folks with broken config) Testing: new UT Docs Changes: n/a Release Notes: n/a Fixes envoyproxy#7767 Signed-off-by: Alyssa Wilk <alyssar@chromium.org>

Removes a stale, unimplemented constructor definition. Risk Level: low Testing: n/a Doc Changes: n/a Release Notes: n/a Signed-off-by: Stephan Zuercher <zuercher@gmail.com>

This is so that Envoy keeps building with the --incompatible_disable_legacy_proto_provider command line option of Bazel which is to be flipped in 1.0 . Description: Risk Level: Testing: Docs Changes: Release Notes: Signed-off-by: Lukacs T. Berki <lberki@google.com>

Omit the node identifier from subsequent discovery requests on the same stream. Restricted to non-incremental xDS for tractability. Risk Level: low, affects xDS protocol but guarded by an option Testing: Unit/integration tests are updated Docs Changes: xDS spec clarification Release Notes: omit the node identifier from subsequent discovery requests Fixes: envoyproxy#7860 Signed-off-by: Kuat Yessenov <kuat@google.com>

To be used with delta ADS. Could probably be used with the current GrpcMuxImpl. Has the SubscriptionCallbacks interface, so a GrpcMux can just directly pass onConfigUpdate() calls through to the WatchMap, which will then appropriately distribute the various resources to the various watches' SubscriptionCallbacks. envoyproxy#4991 Risk Level: none, not yet built into Envoy Testing: unit tests for the new class Signed-off-by: Fred Douglas <fredlas@google.com>

Description: In preparation to implement TCP gRPC Access Logger. Risk Level: Low (refactoring only) Testing: CI Docs Changes: N/A Release Notes: N/A Signed-off-by: Lizan Zhou <lizan@tetrate.io>

…nvoyproxy#7851) Signed-off-by: Dhi Aurrahman <dio@tetrate.io>

…xy#7865) Signed-off-by: Derek Schaller <d_a_schaller@yahoo.com>

Signed-off-by: Xuyang Tao <taoxuy@google.com>

…7904) Signed-off-by: Alyssa Wilk <alyssar@google.com>

Signed-off-by: Lizan Zhou <lizan@tetrate.io>

Signed-off-by: Guangming Wang <guangming.wang@daocloud.io>

Signed-off-by: Cynthia Coan <ccoan@instructure.com>

Description: Upgrade yapf to the latest version. We'd like to reuse it in our local repo, and some of the newer versions contain fixes we need. This required reformatting all the files for their new rules. Happy to change any rules, as necessary. Risk Level: Low Testing: Ensure py format checks can still pass. Docs Changes: N/A Release Notes: N/A fixes envoyproxy#7389 Signed-off-by: Cynthia Coan <ccoan@instructure.com>

Per envoyproxy#7736, we're inadvertently casting a lambda expression to bool. Fortunately, the code is attempting to pass true, so it works. Risk Level: low Testing: n/a Docs Changes: n/a Release Notes: n/a Fixes: envoyproxy#7736 Signed-off-by: Stephan Zuercher <zuercher@gmail.com>

Description: Adds support for DNS SAN as Principal in RBAC filter. Risk Level: Low Testing: Added automated tests Docs Changes: Updated Release Notes: Added Fixes envoyproxy#7836 Signed-off-by: Rama Chavali <rama.rao@salesforce.com>

Signed-off-by: Guangming Wang <guangming.wang@daocloud.io>

…ost weights are equal. (envoyproxy#7877) Only create EdfScheduler for round-robing and least-request load balancers if hosts have different weights. This reduces CPU usage during load balancer creation and memory usage in the common case where all hosts have the same weight. Signed-off-by: Antonio Vicente <avd@google.com>

Signed-off-by: Raul Gutierrez Segales <rgs@pinterest.com>

We pass all environment variables we care about explicitly and should not pass any other not set variables. Signed-off-by: Matt Klein <mklein@lyft.com>

Signed-off-by: Asra Ali <asraa@google.com>

Signed-off-by: Alyssa Wilk <alyssar@chromium.org>

Signed-off-by: Henry Yang <hyang@lyft.com>

Calling out that it's possible to use the value 0 to disable route timeout (as it is for idle timeout). Signed-off-by: nmeessen <nmeessen@atlassian.com>

Signed-off-by: Lizan Zhou <lizan@tetrate.io>

@lizan

…lisk (envoyproxy#7934) Description: Update dependencies: - rules_go 0.19.2 ([release](https://github.com/bazelbuild/rules_go/releases/tag/0.19.2)), [0.19.0 release notes](https://github.com/bazelbuild/rules_go/releases/tag/0.19.0). The big change is that `org_golang_google_grpc` is no longer declared in `go_rules_dependencies`. In order for the API to build, changes to `WORKSPACE` outlined [here](https://github.com/bazelbuild/rules_go/blob/0.19.0/go/workspace.rst#grpc-dependencies) are required. This pollutes `WORKSPACE` with some dependencies. Open on ways to improve this. - Go 1.12.8 (to match rules_go) - various Python updates - curl 7.65.3 ([changelog](https://curl.haxx.se/changes.html#7_65_3)) - bazel-toolchains switches to 0.28.5 release and address @lizan TODO ([changes](bazelbuild/bazel-toolchains@5a8611e...0.28.5)) - bazelisk 1.0 ([release notes](https://github.com/bazelbuild/bazelisk/releases/tag/v1.0)) Risk Level: Low Testing: `./docs/build.sh`, `bazel build @envoy_api//envoy/...`, `bazel test //test/...` Docs Changes: None required Release Notes: None required Signed-off-by: Michael Payne <michael@sooper.org>

…xy#7840) Signed-off-by: Andrew Jenkins <andrew@volunteers.acasi.org>

Signed-off-by: Guangming Wang <guangming.wang@daocloud.io>

…/dynamic config. (envoyproxy#7857) As per envoyproxy#6651, this PR plumbs in CLI options to allow independent control over static/dynamic unknown field validation. The defaults are the same for static as today (strict) and for dynamic we are by default permissive. This permits easy rollout of new API minor versions, including those related to security fixes. Fixes a regression that occurred in envoyproxy#7200 where strict/permissive checking CLI options were inverted. As per envoyproxy#6818, added stats/warning for any unknown fields encountered. Risk level: Low (strictly more permissive by default) Testing: additional unit and integration tests added, exercising both permissive/strict checking over various parts of the API (bootstrap, listeners, clusters, xDS, network filters, etc). Fixes envoyproxy#6651 Fixed envoyproxy#6818 Signed-off-by: Harvey Tuch <htuch@google.com>

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

Fixes envoyproxy#7927. Risk Level: low (test only) Signed-off-by: Piotr Sikora <piotrsikora@google.com>

Introduces a generic expression-based admission filter using https://github.com/google/cel-cpp. This is a follow-up to discussion in envoyproxy#6751. The advantage of this approach is: 1. Un-opinionated about the policy structure since the only config is an expression. This is friendly towards control planes which can bear the complexity of translation, analysis, and evolution of policies. 2. Multi-language, CEL supports go, java, and c++ runtimes. 3. Inter-operability with other filters using request `metadata`. Companion filters can populate metadata about requests and resources that affect policy decisions. 4. Generic utility, it can be used for custom metric labels, access log entries, etc. The dis-advantage of this approach is that its performance is lower than domain-optimized interpreters. On a fair example, the interpreter evaluates in around 1ms (see https://github.com/google/cel-cpp/blob/master/eval/tests/benchmark_test.cc#L591) vs ~150ns for hand-written C++ native code. There is space for improvement (especially if WASM can be used as a compilation target), but ultimately the generic expression form carries a cost. Conditions are added to support RBAC filter for complementing the existing principal/permission model. They add support for the extended checks (e.g. time of query, resource-bound), but add no cost unless used. Description: add expression-based admission filter Risk Level: low Testing: Docs Changes: Release Notes: Signed-off-by: Kuat Yessenov <kuat@google.com>

This adds the ability to specify dynamic metadata (by namespace) to send with the ext_authz check request. This allows one filter to specify information that can be then used in evaluating an authorization decision. Risk Level: Medium. Optional feature/extension of existing filter Testing: Unit testing Docs Changes: Inline in attribute_context.proto and ext_authz.proto Fixes envoyproxy#7699 Signed-off-by: Ben Plotnick <plotnick@yelp.com>

Some speed-ups and validations for codec impl fuzz test: * validate actions aren't empty (another approach would be to scrub / clean these) * limit actions to 1024 * require oneofs Fixes OSS-Fuzz Issue: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=16481 Testing: local asan/libfuzzer exec/sec go from 25 to 50 Signed-off-by: Asra Ali <asraa@google.com>

…#7972) Risk Level: n/a (docs only) Testing: n/a Docs Changes: yes Release Notes: no envoyproxy#7945 Signed-off-by: Alyssa Wilk <alyssar@chromium.org>

…envoyproxy#7958) Description: libc++ std::string may inline the data which results the memory is not aligned to `void*`. Use vector instead to store the optval. Detected by UBSAN with libc++ config. Preparation for envoyproxy#4251 Risk Level: Low Testing: unittest locally Docs Changes: N/A Release Notes: N/A Fixes envoyproxy#7968 Signed-off-by: Lizan Zhou <lizan@tetrate.io>

…voyproxy#7977) * security: some intra-entity and 3rd party embargo clarifications. These came up in the last set of CVEs. Signed-off-by: Harvey Tuch <htuch@google.com>

Include What You Use fix for source/common/protobuf/message_validator_impl.h. Signed-off-by: Andres Guedez <aguedez@google.com>

Signed-off-by: Yuchen Dai <silentdai@gmail.com>

) Route config need deep validation for virtual host duplication check, regex check, per filter config validation etc, which PGV wasn't enough. Risk Level: Low Testing: regression test Docs Changes: N/A Release Notes: N/A Fixes envoyproxy#7939 Signed-off-by: Lizan Zhou <lizan@tetrate.io>

…n O(1… (envoyproxy#7979) Signed-off-by: Xin Zhuang <stevenzzz@google.com>

…nvoyproxy#7984) Signed-off-by: Henry Yang <hyang@lyft.com>

Since binary proto won't have field names, report at least the field numbers, as per https://developers.google.com/protocol-buffers/docs/reference/cpp/google.protobuf.unknown_field_set#UnknownField. Also fix minor typo encountered while doing this work. Risk level: Low Testing: Unit tests added/updated. Fixes envoyproxy#7937 Signed-off-by: Harvey Tuch <htuch@google.com>

Signed-off-by: Manish Kumar <manishjpiet@gmail.com>

…e command-line. (envoyproxy#7882) * Add option to switch between fake and real symbol-tables on the command-line. Signed-off-by: Joshua Marantz <jmarantz@google.com>

Some BUILD files are missing build rules to generate go protos. envoyproxy/go-control-plane depends on these protos, so they should be exposed publicly. Added build rules to generate *.pb.go files. Risk Level: Low Testing: These rules were copied to google3 and tested internally. Unfortunately, I am having a bit of trouble with bazel build directly on these targets ("Package is considered deleted due to --deleted_packages"). Please let me know if there is a better way to test this change. Signed-off-by: Teju Nareddy <nareddyt@google.com>

Xcode 11 requires at least macOS 10.15 (upcoming) in order to use either <experimental/filesystem> or C++17 <filesystem>. Signed-off-by: Piotr Sikora <piotrsikora@google.com>

…envoyproxy#7920) Precursor to envoyproxy#7782 Adding scope tracking functionality to the basic alarm functions. Risk Level: Medium (should be a no-op but is a large enough refactor) Testing: new unit tests Docs Changes: n/a Release Notes: n/a Signed-off-by: Alyssa Wilk <alyssar@chromium.org>

Adds support for DNS SAN in ext authz peer validation Risk Level: Low Testing: Added Docs Changes: Added Release Notes: N/A Signed-off-by: Rama Chavali <rama.rao@salesforce.com>

Description: File access log shouldn't need read access for a file. Risk Level: Low Testing: local in mac, CI Docs Changes: Release Notes: Fixes envoyproxy#7997 Signed-off-by: Lizan Zhou <lizan@tetrate.io>

…on. (envoyproxy#8002) This is part of envoyproxy#7980; basically, we want to leverage the recursive pass that already exists for the deprecated check. This PR does not implement the recursive behavior yet for unknown fields though, because there is a ton of churn, so this PR just has the mechanical bits. We switch plumbing of validation visitor into places such as anyConvert() and instead pass this to MessageUtil::validate. There are a bunch of future followups planned in additional PRs: * Combine the recursive pass for unknown/deprecated check in MessageUtil::validate(). * Add mitigation for envoyproxy#5965 by copying to a temporary before recursive expansion. * [Future] consider moving deprecated reporting into a message validation visitor handler. Risk level: Low Testing: Some new //test/common/protobuf::utility_test unit test. Signed-off-by: Harvey Tuch <htuch@google.com>

) Trusting the x-forwarded-proto header from trusted proxies. If Envoy is operating as an edge proxy but has a trusted hop in front, the trusted proxy should be allowed to set x-forwarded-proto and its x-forwarded-proto should be preserved. Guarded by envoy.reloadable_features.trusted_forwarded_proto, default on. Risk Level: Medium (L7 header changes) but guarded Testing: new unit tests Docs Changes: n/a Release Notes: inline Fixes envoyproxy#4496 Signed-off-by: Alyssa Wilk <alyssar@chromium.org>

…nvoyproxy#7962) Adding a build option to default all deprecated protos off, and using it on the debug build. Risk Level: Low Testing: new UT Docs Changes: inline Release Notes: n/a Fixes envoyproxy#7548 Signed-off-by: Alyssa Wilk <alyssar@chromium.org>

…#8005) Add a parallel native.cc_library to envoy_cc_library for external projects that consume Envoy's libraries. This allows the consuming project to disambiguate overlapping include paths when repository overlaying is used, as it can now include envoy headers via external/envoy/... Risk Level: Low Testing: N/A Signed-off-by: Otto van der Schaaf <oschaaf@we-amp.com>

Builds fuzz targets with asan+libfuzzer and runs them against their corpora. Our native bazel builds work, this PR integrates the asan+libfuzzer builds in to CI. The fuzz target binaries will be in your envoy docker build directory. Invoke with the following for all fuzz targets, or a specified one. ./ci/run_envoy_docker.sh './ci/do_ci.sh bazel.fuzz' ./ci/run_envoy_docker.sh './ci/do_ci.sh bazel.fuzz //test/common/common:utility_fuzz_test' Risk level: low Signed-off-by: Asra Ali asraa@google.com Signed-off-by: Asra Ali <asraa@google.com>

This PR adds BoringSSL private key API abstraction, as discussed in envoyproxy#6248. All comments and discussion is welcomed to get the API sufficient for most private key API tasks. The PR contains the proposed API and the way how it can be used from ssl_socket.h. Also there is some code showing how the PrivateKeyMethodProvider is coming from TLS certificate config. Two example private key method providers are included in the tests. Description: tls: support BoringSSL private key async functionality Risk Level: medium Testing: two basic private key provider implementation Docs Changes: TLS arch doc, cert.proto doc Signed-off-by: Ismo Puustinen <ismo.puustinen@intel.com>

…yproxy#8006) stats: use SymbolTableCreator rather than fakes in a few stray places. (envoyproxy#8006) Signed-off-by: Joshua Marantz <jmarantz@google.com>

This PR contains changes on the xRDS side for SRDS impl, cribbed from http://go/gh/stevenzzzz/pull/8/files#diff-2071ab0887162eac1fd177e89d83175a * Add onConfigUpdate impl for SRDS subscription * Remove scoped_config_manager as it's not used now. * Move ScopedConfigInfo to scoped_config_impl.h/cc * Add a hash to scopeKey and scopeKeyFragment, so we can look up scopekey by hash value in constant time when SRDS has many scopes. * Add a initManager parameter to RDS createRdsRouteConfigProvider API interface, when creating RouteConfigProvider after listener/server warmed up, we need to specify a different initManager than the one from factoryContext to avoid an assertion failure. see related:envoyproxy#7617 This PR only latches a SRDS provider into the connection manager, the "conn manager using SRDS to make route decision" plus integration tests will be covered in a following PR. Risk Level: LOW [not fully implemented]. Testing: unit tests Signed-off-by: Xin Zhuang <stevenzzz@google.com>

Follow-up for envoyproxy#7995. Signed-off-by: Raul Gutierrez Segales <rgs@pinterest.com>

Bulk update of team to match envoyproxy organization. While at it, cleaned up some venv stuff in shell_utils.sh. Risk level: Low Testing: Synced 157 members from envoyproxy to envoyproxy/assignable. Signed-off-by: Harvey Tuch <htuch@google.com>

…ed. (envoyproxy#8018) Signed-off-by: Henry Yang <hyang@lyft.com>

…nvoyproxy#8017) This is a one-time movement of all UDPA content from envoyproxy/envoy to cncf/udpa. The permanent home of UDPA will be https://github.com/cncf/udpa. Risk level: Low Testing: Added UDPA service entry to build_test. Signed-off-by: Harvey Tuch <htuch@google.com>

Signed-off-by: Alyssa Wilk <alyssar@chromium.org>

…voyproxy#8004) Signed-off-by: Rama Chavali <rama.rao@salesforce.com>

…nvoyproxy#7675) Signed-off-by: Kateryna Nezdolii <nezdolik@spotify.com>

This was fixed in envoyproxy#7877 Signed-off-by: Matt Klein <mklein@lyft.com>

Depending on the execution environment in which envoy is being run, it is possible that some of the assumption on the clock are maybe not holding as previously commented. With some sandboxing technologies the clock does not reference the machine boot time but the sandbox boot time. This invalidates the assumtpion that the first update in the cluster_manager will most likely fall out of the windows and ends up showing a non intuitive behavior difficult to catch. This PR simply adds a comment that will allow the reader to consider this option while reading to the code. Signed-off-by: Flavio Crisciani <f.crisciani@gmail.com>

Signed-off-by: Harvey Tuch <htuch@google.com>

The libstdc++ std::regex implementation is not safe in all cases for user provided input. This change deprecates the used of std::regex in all user facing paths and introduces a new safe regex matcher with an explicitly configurable engine, right now limited to Google's re2 regex engine. This is not a drop in replacement for std::regex as all language features are not supported. As such we will go through a deprecation period for the old regex engine. Fixes envoyproxy#7728 Signed-off-by: Matt Klein <mklein@lyft.com>

This is similar to what I did for the arch overview a while ago as this section is also getting out of control. Signed-off-by: Matt Klein <mklein@lyft.com>

Signed-off-by: Harvey Tuch <htuch@google.com>

For debug builds, performance testing and fuzzers reveal that when appending to a header, we scan both the existing value and the data to append for invalid characters. This PR moves the validation check to just the data that is appended, to avoid hangups on re-scanning long header values multiple times. Testing: Added corpus entry that reveals time spent in validHeaderString Signed-off-by: Asra Ali <asraa@google.com>

) During initializing secondary clusters, for each initialized cluster, a ClusterLoadAssignment request is sent to istio pilot with the cluster's name appended into request's resource_names list. With a huge number of clusters(e.g 10k clusters), this behavior slows down Envoy's initialization and consumes ton of memory. This change pauses ADS mux for ClusterLoadAssignment to avoid that. Risk Level: Medium Testing: tiny change, no test case added Fixes envoyproxy#7955 Signed-off-by: lhuang8 <lhuang8@ebay.com>

In theopenlab/openlab-zuul-jobs#622 , the OpenLab add the ability to set the bazel to specific version explicitly. This patch add the bazel role for the envoy job. Signed-off-by: Yikun Jiang <yikunkero@gmail.com>

Add more integration test and additional checks in the unit tests. Signed-off-by: Henry Yang <hyang@lyft.com>

Signed-off-by: Matt Klein <mklein@lyft.com>

…roxy#8038) Risk Level: n/a (test only) Testing: manual Docs Changes: n/a Release Notes: n/a Signed-off-by: Alyssa Wilk <alyssar@chromium.org>

Signed-off-by: Dan Zhang <danzh@google.com>

Description: Initial implementation for TCP gRPC access logger. Risk Level: Low (extension only) Testing: integration test Docs Changes: Added Release Notes: Added Signed-off-by: Lizan Zhou <lizan@tetrate.io>

…nvoyproxy#8023) Signed-off-by: Emil Mikulic <g-easy@users.noreply.github.com>

This allows consuming projects using repository overlaying to disambiguate overlapping include paths when it comes to platform_impl.h by going through envoy/external/... Addendum to envoyproxy#8005 Risk Level: Low Testing: N/A Signed-off-by: Otto van der Schaaf <oschaaf@we-amp.com>

Rather than ASSERT for a reasonably common error condition (e.g. disk full) record a stat that indicates log file writing failed. Also fixes a test race condition. Risk Level: low Testing: added stats checks Docs Changes: documented new stat Release Notes: updated Signed-off-by: Stephan Zuercher <zuercher@gmail.com>

Signed-off-by: Caleb Gilmour <caleb.gilmour@datadoghq.com>

Add PGV bounds to the stats flush interval (greater than 1ms and less than 5000ms) to prevent Envoy from hanging from too small of a flush time. Risk Level: Low Testing: Corpus Entry added Fixes OSS-Fuzz issue https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=16300 Signed-off-by: Asra Ali <asraa@google.com>

Adjust tools/stack_decode.py to more obviously be Python 2 (not 3), and to work on stack traces that don't include the symbol names. Risk Level: Low Testing: Manually tested on a stack trace that one of our users sent us Signed-off-by: Luke Shumaker <lukeshu@datawire.io>

Description: https://github.com/google/googletest/blob/d7003576dd133856432e2e07340f45926242cc3a/BUILD.bazel#L42 Risk Level: Low (test only) Testing: CI Docs Changes: Release Notes: Signed-off-by: Lizan Zhou <lizan@tetrate.io>

…r filter repos (envoyproxy#7907) Description: This change enables using run_envoy_docker.sh to build envoy-filter-example Risk Level: Low Testing: Manually tested building envoy-filter-example using: envoy/ci/run_envoy_docker.sh './ci/do_ci.sh build' Docs Changes: N/A Release Notes: N/A Signed-off-by: Santosh Kumar Cheler <scheler@arubanetworks.com>

Description: the latest glibc (v2.30) declares its own `gettid()` function (see [0]) and this creates a naming conflict in gRPC which has a function with the same name. Apply to gRPC [a patch](grpc/grpc#18950) which renames `gettid()` to `sys_gettid()`. [0] https://sourceware.org/git/?p=glibc.git;a=commit;h=1d0fc213824eaa2a8f8c4385daaa698ee8fb7c92 Risk Level: low Testing: unit tests Docs Changes: n/a Release Notes: n/a Signed-off-by: Dmitry Rozhkov <dmitry.rozhkov@linux.intel.com>

Description: Sanitizers doesn't support static link, reverts envoyproxy#7929 and link lib(std)c++ dynamically in sanitizer runs. Addresses test issue for envoyproxy#4251. Added workaround in ASAN for envoyproxy#7647. Risk Level: Low (test only) Testing: CI, local libc++ runs Docs Changes: N/A Release Notes: N/A Fixes envoyproxy#7928

Using the new runtime utility to clean up a bunch of test gorp. Yay utils! Risk Level: n/a (test only) Testing: tests pass Docs Changes: n/a Release Notes: n/a Signed-off-by: Alyssa Wilk <alyssar@chromium.org>

…y#8057) Making ENVOY_DISABLE_DEPRECATED_FEATURES work for unit tests without runtime configured. Fixing up a handful of unit tests to remove legacy code or use the handy DEPRECATED_FEATURE_TEST macro Adding back coverage of cors.enabled() and redis.catch_all_route() Risk Level: Low (test only) Testing: new unit tests Docs Changes: n/a Release Notes: n/a Fixes envoyproxy#8013 Fixes envoyproxy#7548 Signed-off-by: Alyssa Wilk <alyssar@chromium.org>

Fixes mispelling of `Executioon` -> `Execution` Signed-off-by: Colin Schoen <schoen@yelp.com>

The java_outer_classname is unintentionally duplicated in the new udp_listener_config and regex proto files. This changes them to unique names that match the predominant naming scheme. Signed-off-by: Bryce Anderson <banderson@twitter.com>

…nvoyproxy#8014) Default behavior remains unchanged, but now Envoy can override, override iff there's no server header from upstream, or always leave the server header (or lack thereof) unmodified. Risk Level: low (config guarded change) Testing: new unit tests Docs Changes: n/a Release Notes: inline Fixes envoyproxy#6716 Signed-off-by: Alyssa Wilk <alyssar@chromium.org>

Signed-off-by: Lizan Zhou <lizan@tetrate.io>

RFC2045 (MIME) Base64 decoding support has been fixed upstream Description: The grpc transcoding filter has been updated to support RFC2045 (MIME) based inputs for protobuf type "Bytes". This is important since Base64 is often using the RFC2045 format for inputs. Also see: grpc-ecosystem/grpc-httpjson-transcoding#34 Risk Level: Low Testing: Integration / Manual Tests Docs Changes: N/A Release Notes: N/A Signed-off-by: Hans Viken Duedal <hans.duedal@visma.com>

…e. (envoyproxy#7842) * Convert a few more counter() references to use the StatName interface. Signed-off-by: Joshua Marantz <jmarantz@google.com>

Description: As discussed in envoyproxy#7864 this PR is the attempt to peek the socket at the invoke of onAccept. Usually client_hello packet should be in the buffer when tls_inspector is peeking, we could save a poll cycle for this connection. Once we agree on the solution I can apply to http_inspector as well. The expecting latency improvement especially when poll cycle is large. Benchmark: Env: hardware Intel(R) Xeon(R) CPU @ 2.20GHz envoy: concurrency = 1, tls_inspector as listener filter. One tls filter chain, and one plain text filter chain. load background: a [sniper](https://github.com/lubia/sniper) client with concurrency = 5 hitting the server with tls handshake, aiming to hit using the tls_filter chain. The qps is about 170/s Another load client hitting the plain text filter chain but would go through tls_inspector with concurrency = 1 This PR: TransactionTime: 10.3 - 11.0 ms(mean) Master TransactionTime: 12.3 - 12.8 ms(mean) Risk Level: Med (ActiveSocket code is affected to adopt the side effect of onAccept) Testing: Docs Changes: Release Notes: Fixes envoyproxy#7864 Signed-off-by: Yuchen Dai <silentdai@gmail.com>

…Up hiding base-class virtual functions (envoyproxy#8071) Description: I'm seeing "bazel-out/k8-fastbuild/bin/external/com_github_google_benchmark/_virtual_includes/benchmark/benchmark/benchmark.h:1071:16: error: 'virtual void benchmark::Fixture::SetUp(benchmark::State&)' was hidden" when running tests. This resolves the issue with hiding of the base-class functions. Risk Level: low Testing: Docs Changes: Release Notes: Signed-off-by: Dmitri Dolguikh <ddolguik@redhat.com>

Takeaways: we've lost the ability to do empty regex (which was covered in router tests and is proto constraint validated on the new safe regex) as well as negative lookahead (also covered in tests) along with a host of other things conveniently documented as not supported here: https://github.com/google/re2/wiki/Syntax Otherwise split up a bunch of tests, duplicated and tagged a bunch of tests, and cleaning up after we finally can remove deprecated fields again will be an order of magnitude easier. Also fixing a dup relnote from envoyproxy#8014 Risk Level: n/a (test only) Testing: yes. yes there is. Docs Changes: no Release Notes: no Signed-off-by: Alyssa Wilk <alyssar@chromium.org>

…y#8072) Signed-off-by: Teju Nareddy <nareddyt@google.com>

Update QUICHE tar ball to 4abb566fbbc63df8fe7c1ac30b21632b9eb18d0c. Add some new impl's for newly added api. Risk Level: low Testing: using quiche build in tests. Part of envoyproxy#2557 Signed-off-by: Dan Zhang <danzh@google.com>

We need a way to run the deprecated field check on the RouteConfiguration. Today the schema check tool validates the bootstrap config. This change will help achieve similar functionality on routes served from rds. Risk Level: Low Testing: Manual testing Docs Changes: included Release Notes: included Signed-off-by: Jyoti Mahapatra <jmahapatra@lyft.com>

…#6985) Description: This patch supports sending a list of spans as JSON v2 and protobuf message over HTTP to Zipkin collector. [Sending protobuf](https://github.com/openzipkin/zipkin-api/blob/0.2.1/zipkin.proto) is considered to be more efficient than JSON, even compared to the v2's JSON (openzipkin/zipkin#2589 (comment)). This is an effort to rework envoyproxy#6798. The approach is by serializing the v1 model to both v2 JSON and protobuf. Risk Level: Low, since the default is still HTTP-JSON v1 based on https://github.com/openzipkin/zipkin-api/blob/0.2.2/zipkin-api.yaml. Testing: Unit testing, manual integration test with real Zipkin collector server. Docs Changes: Added Release Notes: Added Fixes: envoyproxy#4839 Signed-off-by: Dhi Aurrahman <dio@tetrate.io> Signed-off-by: José Carlos Chávez <jcchavezs@gmail.com>

…proxy#8101) Signed-off-by: Jyoti Mahapatra <jmahapatra@lyft.com>

Description: add Scoped RDS routing logic into HCM. Changes include: * in ActiveStream constructor latch a ScopedConfig impl to the activeStream if SRDS is enabled * in the beginning of ActiveStream::decodeHeaders(headers, end_stream), get routeConfig from latched ScopedConfig impl. This PR is the 3rd in the srds impl PR chain: [envoyproxy#7704, envoyproxy#7451, this]. Risk Level: Medium Testing: unit test and integration tests. Release Notes: Add scoped RDS routing support into HCM. Signed-off-by: Xin Zhuang <stevenzzz@google.com>

@asraa

* @asraa is joining Envoy OSS security team. * @lambdai is joining Friends of Envoy as v2 xDS point. Signed-off-by: Harvey Tuch <htuch@google.com>

This PR unifies the recursive traversal of deprecated fields with that of unknown fields. It doesn't deal with moving to a validator visitor model for deprecation; this would be a nice cleanup that we track at envoyproxy#8092. Risk level: Low Testing: New nested unknown field test added. Fixes envoyproxy#7980 Signed-off-by: Harvey Tuch <htuch@google.com>

This PR allows the envoy_cc_fuzz_test rule to be used when pulling in envoy. which can be useful when you're writing filters for envoy, and want to reuse the fuzzing architecture envoy has already built. other rules already allow for this (see envoy_cc_test in this same file for example). Risk Level: Low Testing: Testing the Old Rule Still Works It is possible to test the old rules still work (even without specifying a repository), by simply choosing your favorite fuzz test, and choosing to run bazel test on it. For example: bazel test //test/common/router:header_parser_fuzz_test. Any envoy_cc_fuzz_test rule should do. Testing New Rules Work I've done testing inside my own repository, but if you want to create your own test rule you can probably do the following in envoy-filter-example: Checkout envoy-filter-example, and update the envoy submodule to this pr. Follow the directions in: test/fuzz/README.md to define a envoy_cc_fuzz_test rule. Make sure to add a line for: repository = "@envoy" which is the new argument being added. You should be able to run the fuzz test. Signed-off-by: Cynthia Coan <ccoan@instructure.com>

…y#8113) Fixes envoyproxy#8112 Signed-off-by: John Millikin <jmillikin@stripe.com>

…e class HttpIntegrationTest (envoyproxy#8108) Fixes envoyproxy#8050 Risk Level: LOW [refactor only] Signed-off-by: Xin Zhuang <stevenzzz@google.com>

…uster modification (envoyproxy#8106) Risk Level: Medium Testing: New unit test added. Fix verified via --config=asan. Signed-off-by: Andres Guedez <aguedez@google.com>

…nvoyproxy#8080) * api:Add a flag to disable overprovisioning in ClusterLoadAssignment Signed-off-by: Jie Chen <jiechen@google.com> * api:Add [#next-major-version and [#not-implemented-hide to the comment for field of disable_overprovisioning in ClusterLoadAssignment Signed-off-by: Jie Chen <jiechen@google.com> * api:Refine comments for the new added bool flag as suggested. Signed-off-by: Jie Chen <jiechen@google.com>

This patch establishes a v3alpha baseline API, by doing a simple copy of v2[alpha] dirs and some sed-style heuristic fixups of BUILD dependencies and proto package namespaces. The objective is provide a baseline which we can compare the output from tooling described in envoyproxy#8083 in later PRs, providing smaller visual diffs. The core philosophy of the API migration is that every step will be captured in a script (at least until the last manual steps), api/migration/v3alpha.sh. This script will capture deterministic migration steps, allowing v2[alpha] to continue to be updated until we finalize v3. There is likely to be significant changes, e.g. in addition to the work scoped for v3, we might want to reduce the amount of API churn by referring back to v2 protos where it makes sense. This will be done via tooling in later PRs. Part of envoyproxy#8083. Risk level: Low Testing: build @envoy_api//... Signed-off-by: Harvey Tuch <htuch@google.com>

Description: The heartbeat packet may carry data, and it is treated as null data when processing the heartbeat packet, causing some data to remain in the buffer. Risk Level: low Testing: Existing unit test Docs Changes: N/A Release Notes: N/A Fixes envoyproxy#7970 Signed-off-by: tianqian.zyf <tianqian.zyf@alibaba-inc.com>

* shared the main symbol-table with the isolated stats used for cluster info. Signed-off-by: Joshua Marantz <jmarantz@google.com>

Risk level: Low Testing: Rebuilt docs, manual inspection of some example generated files. Signed-off-by: Harvey Tuch <htuch@google.com>

This avoids having to list new docs protos in both docs/build.sh and api/docs/BUILD. This technical debt cleanup is helpful in v3 proto work to simplify collecting proto artifacts from a Bazel aspect. Risk level: Low Testing: docs/build.sh, visual inspection of docs. Signed-off-by: Harvey Tuch <htuch@google.com>

Fixes envoyproxy#7982 Defines a package level proto library and its associated internal go_proto_library. Deletes all existing api_go_proto_library, api_go_grpc_library, and go_package annotations in protos (they are not required and pollute the sources). I deliberately avoided touching anything under udpa since it's being moved to another repository. Risk Level: low Testing: build completes Signed-off-by: Kuat Yessenov <kuat@google.com>

These were missed in envoyproxy#8125. Signed-off-by: Harvey Tuch <htuch@google.com>

Old versions of bash (e.g. on macOS) don't handle ${P/:/\/} the same way as modern versions. In particular, the expanded parameter on macOS includes a backslash, causing subsequent use of the string as a filename to include a slash (/) instead of treating the slash as a directory separator. Both versions of bash accept ${P/://} as a way to substitute : with /. Verified that this change does not alter the generated docs when running under Linux. Risk Level: low Testing: generated docs under linux & macOS Signed-off-by: Stephan Zuercher <zuercher@gmail.com>

…oyproxy#7981) Description: When a request comes in on http1 with "upgrade: h2c", the current behavior is to 503. Instead we should ignore the upgrade and remove the header and continue with the request as http1. Risk Level: Medium Testing: Unit test. Hand test with ithub.com/rdsubhas/java-istio client server locally. Docs Changes: N/A Release Notes: http1: ignore and remove Upgrade: h2c. Fixes istio/istio#16391 Signed-off-by: John Plevyak <jplevyak@gmail.com>

) Because of rules_foreign_cc in bazelbuild, Envoy will not compile successfully when following the instructions in the build docs due to how the tools are referenced. One fix for this is installing Xcode from the App Store (see bazel-contrib/rules_foreign_cc#185). Risk Level: Low Testing: N/A (docs change) Docs Changes: see Description Release Notes: N/A Signed-off-by: Lisa Lu <lisalu@lyft.com>

envoyproxy#8138) As discussed in envoyproxy#8127, some custom header expressions evaluate as empty when used in request headers. Risk Level: low, docs only Testing: n/a Docs Changes: updated Release Notes: n/a Signed-off-by: Stephan Zuercher <zuercher@gmail.com>

…xy#7999) Use the listener-level field for the tracing direction over the per-filter field. Unfortunately, the per filter did not provide an "unspecified" default, so this appears to be the right approach to deprecate the per-filter field with minimal impact. Risk Level: low (uses a newly introduce field traffic_direction) Testing: unit test Docs Changes: proto docs Signed-off-by: Kuat Yessenov <kuat@google.com>

Istio sets listener filter timeout to 10ms by default but requests fail from time to tome. It's very difficult to debug. Even though downstream_pre_cx_timeout_ is exposed to track the number of timeouts, it would be better to have some debug logs. Description: add more diagnostic logs Risk Level: low Signed-off-by: crazyxy <yxyan@google.com>

…8095) This PR adds a configuration option for controlling the length of the request path that is included in the HttpUrl span tag. Currently, this length is hard-coded to 256. With this PR, that length will be configurable (defaulting to the old value). Risk Level: Low Testing: Unit Docs Changes: Inline with the API proto. Documented new field. Release Notes: Added in the PR. Related issue: istio/istio#14563 Signed-off-by: Douglas Reid <douglas-reid@users.noreply.github.com>

This PR adds fields to CDS that allow for general-purpose LB policy configuration. Risk Level: Low Testing: None (but if anything is needed, please let me know) Docs Changes: Inline with API protos Release Notes: N/A Signed-off-by: Mark D. Roth <roth@google.com>

Transport/protocol decoder errors that occur before the connection manager initializes an ActiveRPC to track the request caused a crash. Modifies the connection manager to handle this case, terminating the downstream the connection. Risk Level: low Testing: test case that triggers crash Docs Changes: n/a Release Notes: added Signed-off-by: Stephan Zuercher <zuercher@gmail.com>

Remove gogoproto annotations. They can be replaced with a custom gogoproto compiler (e.g. something like https://github.com/gogo/googleapis/tree/master/protoc-gen-gogogoogleapis). I have an experimental version of it to validate that it's possible to re-apply important annotations in the compiler. Risk Level: low Testing: builds Signed-off-by: Kuat Yessenov <kuat@google.com>

…start_test (envoyproxy#8162) In the server config file `test/config/integration/server.yaml` used by //test/integration:hotrestart_test, `dynamic_resources` includes `lds_config` and `cds_config` definitions, which use HTTP API to fetch config, but CDS and LDS service do not exist, so the initial fetch will be failed with a connection failure, then Envoy server continue startup. Envoy server shouldn't continue startup because connection failure, see issue envoyproxy#8046. For this test, `dynamic_resources` is not needed, this change clean it up. Signed-off-by: lhuang8 <lhuang8@ebay.com>

Description: clang-tidy check to flag unused using statements. There's a lot in test code that's just copy pasta, and it's hard to manually review whether it's being used, especially for things like using testing::_; Risk Level: low Testing: existing Docs Changes: N/A Release Notes: N/A Signed-off-by: Derek Argueta <dereka@pinterest.com>

Build curl dependency with async DNS resolver c-ares avoiding potential crashes due to longjmp on modern kernels. Add zlib and nghttp2. Use Envoy's version of all of the above libraries. Signed-off-by: Taras Roshko <troshko@netflix.com>

Description: add upstream TLS info for logging purposes Refactor SSL connection info to be a shared pointer. Use read-only interface. Cache computed values in the SSL info object (this allows transition to remove the underlying SSL object if necessary). Risk Level: medium due to use of bssl::SSL to back ConnectionInfo Testing: unit Docs Changes: none Release Notes: add upstream TLS info Signed-off-by: Kuat Yessenov <kuat@google.com>

Add missing destructor to class declaration. Fix copy/paste errors. These errors were apparently introduced in e1cd4cc. Risk Level: Low Testing: Passed Windows testing locally Docs Changes: n/a Release Notes: n/a Signed-off-by: William Rowe wrowe@pivotal.io Signed-off-by: Yechiel Kalmenson <ykalmenson@pivotal.io>

Signed-off-by: Pengyuan Bian <bianpengyuan@google.com>

…proxy#7942) Signed-off-by: ZhouyihaiDing <ddyihai@google.com>

Signed-off-by: Derek Argueta <dereka@pinterest.com>

Making it clear H2 websockets don't work by default Risk Level: n/a Testing: n/a Docs Changes: yes Release Notes: no envoyproxy#8147 Signed-off-by: Alyssa Wilk <alyssar@chromium.org>

…yproxy#8020) Description: Upstream from envoyproxy/envoy-wasm the WebAssembly VM support along with the Null VM support and tests. This is the first PR dealing with WebAssembly filter support in envoy. See https://github.com/envoyproxy/envoy-wasm/blob/master/WASM.md and https://github.com/envoyproxy/envoy-wasm/blob/master/docs/root/api-v2/config/wasm/wasm.rst for details. Risk Level: Medium Testing: Unit tests. Docs Changes: N/A Release Notes: N/A Part of envoyproxy#4272 Signed-off-by: John Plevyak <jplevyak@gmail.com>

Implement QuicStream|Session|Disptacher in Envoy. Weir up QUIC stream and connection with HCM callbacks. Risk Level: low, not in use Testing: Added unit tests for all new classes Part of envoyproxy#2557 Signed-off-by: Dan Zhang <danzh@google.com>

…yproxy#8157) Split out the generic plugin and FileDescriptorProto traversal bits from protodoc. This is in aid of the work in envoyproxy#8082 ad envoyproxy#8083, where additional protoc plugins will be responsible for v2 -> v3alpha API migrations and translation code generation. This is only the start really of the api_proto_plugin framework. I anticipate additional bits of protodoc will move here later, including field type analysis and oneof handling. In some respects, this is a re-implementation of some of https://github.com/lyft/protoc-gen-star in Python. The advantage is that this is super lightweight, has few dependencies and can be easily hacked. We also embed various bits of API business logic, e.g. annotations, in the framework (for now). Risk level: Low Testing: diff -ru against previous protodoc.py RST output, identical modulo some trivial whitespace that doesn't appear in generated HTML. There are no real tests yet, I anticipate adding some golden proto style tests. Signed-off-by: Harvey Tuch <htuch@google.com>

) Signed-off-by: Tony Allen <tallen@lyft.com>

…8144) Signed-off-by: Dhi Aurrahman <dio@tetrate.io>

Description: Follow-up to envoyproxy#7911 to make cached values be exposed as const-references, saving on a copy of a string during retrieval. Risk Level: low Testing: updated mocks to return references Docs Changes: none Release Notes: none Signed-off-by: Kuat Yessenov <kuat@google.com>

Add a test ensuring curl was built with the expected features. Description: Add a test ensuring curl was built with the expected features. Risk Level: Low. Testing: n/a. Docs Changes: n/a. Release Notes: n/a. Signed-off-by: Taras Roshko <troshko@netflix.com>

…#8030) * subset lb: allow ring hash/maglev LB to work with subsets Skip initializing the thread aware LB for a cluster when the subset load balancer is enabled. Also adds some extra checks for LB policies that are incompatible with the subset load balancer. Risk Level: low Testing: test additional checks Docs Changes: updated docs w.r.t subset lb compatibility Release Notes: n/a Fixes: envoyproxy#7651 Signed-off-by: Stephan Zuercher <zuercher@gmail.com>

Signed-off-by: Nicolas Flacco <nflacco@lyft.com>

Description: Upgrade bazel to 0.29.1 and bazel-toolchains to corresponding version. Risk Level: Low Testing: CI Docs Changes: N/A Release Notes: N/A Signed-off-by: Lizan Zhou <lizan@tetrate.io>

…oxy#8024) Previously, when in a panic state, requests would be routed to all hosts. In some cases it is instead preferable to not route any requests. Add a configuration option for zone-aware load balancers which switches from routing to all hosts to no hosts. Closes envoyproxy#7550. Signed-off-by: James Forcier jforcier@grubhub.com Risk Level: Low Testing: 2 new unit tests written; manual testing Docs Changes: Note about new configuration option added Release Notes: added Signed-off-by: James Forcier <jforcier@grubhub.com>

Signed-off-by: Rama Chavali <rama.rao@salesforce.com>

Signed-off-by: Pengyuan Bian <bianpengyuan@google.com>

…nvoyproxy#8189) Signed-off-by: Antonio Vicente <avd@google.com>

…y#8160) Signed-off-by: Lisa Lu <lisalu@lyft.com>

Description: Looks like the runtime docs moved under operations/. The PR fixes the link. Risk Level: low Testing: existing Docs Changes: this Release Notes: n/a Signed-off-by: Derek Argueta <dereka@pinterest.com>

…llThreads interface to Slot. (envoyproxy#8135) See the issue in envoyproxy#7902, this PR is to make the SlotImpl detachable from its owner, by introducing a Booker object wraps around a SlotImpl, which bookkeeps all the on-the-fly update callbacks. And on its destruction, if there are still on-the-fly callbacks, move the SlotImpl to an deferred-delete queue, instead of destructing the SlotImpl which may cause an SEGV error. More importantly, introduce a new runOnAllThreads(ThreadLocal::UpdateCb cb) API to Slot, which requests a Slot Owner to not assume that the Slot or its owner will out-live (in Main thread) the fired on-the-fly update callbacks, and should not capture the Slot or its owner in the update_cb. Picked RDS and config-providers-framework as examples to demonstrate that this change works. {i.e., changed from the runOnAllThreads(Event::PostCb) to the new runOnAllThreads(TLS::UpdateCb) interface. } Risk Level: Medium Testing: unit test Docs Changes: N/A Release Notes: N/A [Optional Fixes #Issue] envoyproxy#7902 Signed-off-by: Xin Zhuang <stevenzzz@google.com>

…y#8203) Build the config programmatically to make future API changes less onerous. Risk Level: low (test change only) Testing: n/a Doc Changes: n/a Release Notes: n/a Signed-off-by: Stephan Zuercher <zuercher@gmail.com>

…on (envoyproxy#8186) Signed-off-by: Fred Douglas <fredlas@google.com>

…envoyproxy#8166) Signed-off-by: Henry Yang <hyang@lyft.com>

…ater than zero (envoyproxy#8089) Signed-off-by: Nicolas Flacco <nflacco@lyft.com>

As well as being a nice cleanup, this fixes some issues I had with local Docker use of fix_format as a non-root user. Signed-off-by: Harvey Tuch <htuch@google.com>

…nvoyproxy#8179) Signed-off-by: Joshua Marantz <jmarantz@google.com>

Signed-off-by: Daniel Grimm <dgrimm@redhat.com>

…8130) Description: Add a new outlier detection mode which compares each host's rate of request failure to a configured fixed threshold. Risk Level: Low Testing: 2 new unit tests added. Docs Changes: New mode and config options described. Release Notes: white_check_mark Fixes envoyproxy#8105 Signed-off-by: James Forcier <jforcier@grubhub.com>

…36cf26b-merge

Merge attempt to upstream/36cf26b9d6ac32f5671c24b92f9ea22ab70bc6c1 #1

Merge attempt to upstream/36cf26b9d6ac32f5671c24b92f9ea22ab70bc6c1 #1

Commits on Aug 1, 2019

Commits on Aug 2, 2019

Commits on Aug 3, 2019

Commits on Aug 5, 2019

Commits on Aug 6, 2019

Commits on Aug 7, 2019

Commits on Aug 8, 2019

Commits on Aug 9, 2019

Commits on Aug 11, 2019

Commits on Aug 12, 2019

Commits on Aug 13, 2019

Commits on Aug 14, 2019

Commits on Aug 15, 2019

Commits on Aug 16, 2019

Commits on Aug 19, 2019

Commits on Aug 20, 2019

Commits on Aug 21, 2019

Commits on Aug 22, 2019

Commits on Aug 23, 2019

Commits on Aug 25, 2019

Commits on Aug 26, 2019

Commits on Aug 27, 2019

Commits on Aug 28, 2019

Commits on Aug 29, 2019

Commits on Aug 30, 2019

Commits on Sep 2, 2019

Commits on Sep 3, 2019

Commits on Sep 4, 2019

Commits on Sep 5, 2019

Commits on Sep 6, 2019

Commits on Sep 7, 2019

Commits on Sep 8, 2019

Commits on Sep 9, 2019

Commits on Sep 10, 2019

Commits on Sep 11, 2019

Commits on Sep 12, 2019

Commits on Sep 13, 2019