The gRPC xDS implementation uses hardcoded retry durations for re-establishing the gRPC channel. This change makes the backoff parameters configurable.
Risk Level: Low
Testing: unit test
Fixes#24236
Signed-off-by: Jayson Dmello <jdmello@confluent.io>
Mirrored from https://github.com/envoyproxy/envoy @ 672b41532a9f03bc84fbbfec0d1db5b633833f9c
Commit Message:
Additional Description: Follow up to #26155, enabling a similar feature for upstream access logs - record an access log on upstream connection established, if requested.
Risk Level: Low
Testing: Unit tests, integration tests
Docs Changes: router API
Release Notes: none
Platform Specific Features: none
Signed-off-by: Ohad Vano <ohadvano@gmail.com>
Signed-off-by: ohadvano <49730675+ohadvano@users.noreply.github.com>
Mirrored from https://github.com/envoyproxy/envoy @ 49a2fc0e4dbfd608737d06ab0a9b94ca4fc73104
Commit Message: Adds a protocol option for which HTTP/2 codec to use.
Additional Description:
Risk Level: low
Testing: ran unit tests and integration tests locally
Docs Changes: n/a
Release Notes: n/a
Platform Specific Features:
Signed-off-by: Biren Roy <birenroy@google.com>
Mirrored from https://github.com/envoyproxy/envoy @ 73115db835f27a79a79a44b8ee8f7ac4333891c7
Commit Message: Allow only histogram summaries in metric service
Additional Description: Histogram metrics by default send two metrics Summary (containing quantiles) and Histogram (containing all the buckets), this makes payloads extremely large when handling lots of stats. In some cases, only having the summary is enough, since we can get sum, count, and percentiles. Furthermore, it probably only makes sense to send one of both, if I were to need buckets, then Summary is probably useless.
Risk Level: low, off by default
Testing:
Docs Changes:
Release Notes:
Platform Specific Features:
Signed-off-by: Sebastian Schepens <sebastian.schepens@mercadolibre.com>
Mirrored from https://github.com/envoyproxy/envoy @ c40aca4c1b51f2089fd33e70b393041c6b291064
Add a new optional field to TlsParameters to configure signature algorithms.
The value is used during TLS handshake in TLS Signature Algorithms extension.
It indicates which signature algorithms may be used for digital signatures.
The value can be used for both DownstreamTlsContext and UpstreamTlsContext.
Signed-off-by: Tero Saarni <tero.saarni@est.tech>
Mirrored from https://github.com/envoyproxy/envoy @ 084794dd06c36edbcb27e05dc06c9d56a72b403f
* accesslog: add fields to ALS proto
Signed-off-by: Lex Herbert <lex.herbert@gmail.com>
* update code to match proto changes
Signed-off-by: Lex Herbert <lex.herbert@gmail.com>
* address PR feedback
Signed-off-by: Lex Herbert <lex.herbert@gmail.com>
---------
Signed-off-by: Lex Herbert <lex.herbert@gmail.com>
Mirrored from https://github.com/envoyproxy/envoy @ a565b6e68ab269540a16c03fa5a6183d0cb3094f
This can help ext_proc server to extend the timeout value in case it needs more time to process a request in special situations like cold start a WASM module when receives the first request.
Risk level: Low
Testing: Integration tests.
Signed-off-by: Yanjun Xiang <yanjunxiang@google.com>
Mirrored from https://github.com/envoyproxy/envoy @ f23c23e24264bfe0bf9453a071ec7040f79dc347
Signed-off-by: Stefan Schönbächler <stefan@schonbachler.org>
Mirrored from https://github.com/envoyproxy/envoy @ 4e6956f77ce9685237f9a523e0aa59ef5f171455
add support for warm on init flag for redis cluster
Signed-off-by: Rama Chavali <rama.rao@salesforce.com>
Mirrored from https://github.com/envoyproxy/envoy @ bb546b0e65932a47d160b0b6e676f43381d6aa00
* Add disabled option to cache filter
Signed-off-by: Raven Black <ravenblack@dropbox.com>
* Avoid constructing OptRef from nullptr
Signed-off-by: Raven Black <ravenblack@dropbox.com>
* Disabled test should use cacheable request
Signed-off-by: Raven Black <ravenblack@dropbox.com>
* Don't use oneof, make disabled separate
Signed-off-by: Raven Black <ravenblack@dropbox.com>
* No longer using validate.proto
Signed-off-by: Raven Black <ravenblack@dropbox.com>
* Add use-cases to disabled field doc
Signed-off-by: Raven Black <ravenblack@dropbox.com>
* Doc formatting better
Signed-off-by: Raven Black <ravenblack@dropbox.com>
* Use ref link
Signed-off-by: Raven Black <ravenblack@dropbox.com>
---------
Signed-off-by: Raven Black <ravenblack@dropbox.com>
Mirrored from https://github.com/envoyproxy/envoy @ c430a5ab8f0e83c057ee3df0f8e836f45d39d759
Commit Message: http: periodic HCM access logs
Additional Description: Make it possible to log periodically from the HCM. This parallels the work already done in TcpProxy.
Risk Level: low
Testing: unit tests.
Docs Changes: none
Mirrored from https://github.com/envoyproxy/envoy @ e11d5de33e342400a8102dcdfabad48b7da987b7
Client-wide WRR added with #24520 needs to support the weight penalty using the error rate. This change adds a parameter that configures this behavior.
Risk Level: Low
Testing: N/A
Signed-off-by: Yousuk Seung <ysseung@google.com>
Mirrored from https://github.com/envoyproxy/envoy @ d5ab0a64c7924e526842f6edd1e5a3a7615fd221
Signed-off-by: Adam Kotwasinski <adam.kotwasinski@gmail.com>
Mirrored from https://github.com/envoyproxy/envoy @ 5e83af5042ec4ff87cad9d3baf476fbd57a7d048
If present, force http-parser (if value is false) or BalsaParser (if value is true). If not present, parser is selected based on envoy.reloadable_features.http1_use_balsa_parser.
Tracking issue: #21245
Signed-off-by: Bence Béky bnc@google.com
Commit Message: [balsa] Add Http1ProtocolOptions field to override HTTP/1 parser.
Additional Description:
Risk Level: low
Testing: n/a
Docs Changes: n/a
Release Notes: n/a
Platform Specific Features: n/a
Signed-off-by: Bence Béky <bnc@google.com>
Mirrored from https://github.com/envoyproxy/envoy @ 80530fd0a32e242327c684cfe262d88e0f5eacbb
There are some issues/quesions about the cors filter usage. And this PR do a minor update to the cors filter's docs and example to clarify the function and latest recommend usage of cors filter.
Risk Level: low.
Testing: n/a.
Signed-off-by: wbpcode <wangbaiping@corp.netease.com>
Mirrored from https://github.com/envoyproxy/envoy @ acd218e1d96a64fd9300977e38d5f5398422b820
Commit Message: adding filter state matching input
Additional Description: Adding a matching input of type 'FilterStateInput', that retrieves a specific filter state object by a given key and uses the serialized value as a matching candidate.
Risk Level: low
Testing: unit and integration tests
Docs Changes: matcher_api
Release Notes: none
Platform Specific Features: none
Mirrored from https://github.com/envoyproxy/envoy @ f52d559e0479824b9c964e4c028fa373bcb9b767
data-plane-api(Azure Pipelines)