Chiebot-Mirror
/
data-plane-api
mirror of https://github.com/envoyproxy/data-plane-api.git
8
0
Fork 0
Code Issues Projects Releases Wiki Activity
[READ ONLY MIRROR] Envoy REST/proto API definitions and documentation. (grpc依赖)
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
2278 Commits
2 Branches
0 Tags
17 MiB
Tag: Branch: Tree: dcf87698a8
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'dcf87698a8'
${ noResults }
data-plane-api/BUILD

347 lines
18 KiB
Raw Normal View History Unescape

api: Revert #17536 as proto_format expects the header to be there (#17548) Signed-off-by: Ryan Northey <ryan@synca.io> Mirrored from https://github.com/envoyproxy/envoy @ 93b58ed0bd897c16d42b30e2ef016a6d491e7e8b
3 years ago
# DO NOT EDIT. This file is generated by tools/proto_format/proto_sync.py.
tooling: Optimize `config_validation` (#21607) Signed-off-by: Ryan Northey <ryan@synca.io> Mirrored from https://github.com/envoyproxy/envoy @ 2b2a08b23611a7a77942e1a203b24a0ebb1698df
2 years ago
load("@rules_proto//proto:defs.bzl", "proto_descriptor_set", "proto_library")
tools: API boosting support for renames. (#9442) The type database now has rename information. Also some misc. fixes for enum and generated static method handling support. Part of #8082 Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 2c8992bce1880ed7ae8ede837434b8713c24a615
5 years ago
licenses(["notice"]) # Apache 2
proto_library(
api/docs: v3 API reference documentation. (#9719) This PR introduces a parallel v3 API reference documentation tree to the existing v2 one. The docs/root/api-v3/ tree was copied from docs/root/api-v2 and the necessary package path fixups were made manually. As a result, the tree largely resembles the v2 docs. Long term this is likely to evolve to reflect the shape of the new extensions tree. The message type, field and enum anchors are sed'ed to be distinct and self-consistent inside api-v3/. There were a number of API proto changes that were made to obtain a successful Sphinx build: * References to deprecated fields were replaced by references to the replacement field. * clang-format line wrapping in protoxform was removed, this breaks RST in some v3 protos. * Some packages (type/metadata/v2, data/cluster/v2alpha) were force upgraded to v3, to deal with references to types that are distinct in v2/v3. This is OK as these packages probably make sense to bump for v3, in general we're going to have to think about how to do this more cleanly, supporting dual v2/v3 references alongside each other. * Some evil hacks for field renaming added to migrate.py for RouteAction. There's also some additional machinery added to compute distinct v3/v3 build targets to point protodoc at. Risk level: Low Testing: Docs build, manual inspection. Fixes #8087 Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ ac88316892cd47b6a9b58e3736e20e8863cd0d27
5 years ago
name = "v2_protos",
tools: API boosting support for renames. (#9442) The type database now has rename information. Also some misc. fixes for enum and generated static method handling support. Part of #8082 Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 2c8992bce1880ed7ae8ede837434b8713c24a615
5 years ago
visibility = ["//visibility:public"],
deps = [
"//envoy/admin/v2alpha:pkg",
"//envoy/api/v2:pkg",
"//envoy/api/v2/auth:pkg",
"//envoy/api/v2/cluster:pkg",
"//envoy/api/v2/core:pkg",
"//envoy/api/v2/endpoint:pkg",
"//envoy/api/v2/listener:pkg",
"//envoy/api/v2/ratelimit:pkg",
"//envoy/api/v2/route:pkg",
"//envoy/config/bootstrap/v2:pkg",
api: remove v2 dependencies from v3 API protos. (#18817) This should reduce the binary size, which is particularly important for Envoy Mobile. Looking at a local opt build with debug symbols, I'm seeing a drop from ~400MB to ~380MB, so maybe 5% saving. @Reflejo indicates that optimized Envoy Mobile without symbols is observing ~20% improvement. Related to #10943 Risk level: Low Testing: bazel query deps to confirm no more v2 API deps. Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 53fca618e47702f6c8dbc323db9bd39d15725457
3 years ago
"//envoy/config/cluster/dynamic_forward_proxy/v2alpha:pkg",
"//envoy/config/common/dynamic_forward_proxy/v2alpha:pkg",
"//envoy/config/common/tap/v2alpha:pkg",
tools: API boosting support for renames. (#9442) The type database now has rename information. Also some misc. fixes for enum and generated static method handling support. Part of #8082 Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 2c8992bce1880ed7ae8ede837434b8713c24a615
5 years ago
"//envoy/config/filter/accesslog/v2:pkg",
"//envoy/config/filter/fault/v2:pkg",
api: remove v2 dependencies from v3 API protos. (#18817) This should reduce the binary size, which is particularly important for Envoy Mobile. Looking at a local opt build with debug symbols, I'm seeing a drop from ~400MB to ~380MB, so maybe 5% saving. @Reflejo indicates that optimized Envoy Mobile without symbols is observing ~20% improvement. Related to #10943 Risk level: Low Testing: bazel query deps to confirm no more v2 API deps. Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 53fca618e47702f6c8dbc323db9bd39d15725457
3 years ago
"//envoy/config/filter/http/compressor/v2:pkg",
"//envoy/config/filter/http/dynamic_forward_proxy/v2alpha:pkg",
"//envoy/config/filter/http/gzip/v2:pkg",
"//envoy/config/filter/http/rate_limit/v2:pkg",
"//envoy/config/filter/http/rbac/v2:pkg",
"//envoy/config/filter/network/dubbo_proxy/v2alpha1:pkg",
tools: API boosting support for renames. (#9442) The type database now has rename information. Also some misc. fixes for enum and generated static method handling support. Part of #8082 Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 2c8992bce1880ed7ae8ede837434b8713c24a615
5 years ago
"//envoy/config/filter/network/http_connection_manager/v2:pkg",
api: remove v2 dependencies from v3 API protos. (#18817) This should reduce the binary size, which is particularly important for Envoy Mobile. Looking at a local opt build with debug symbols, I'm seeing a drop from ~400MB to ~380MB, so maybe 5% saving. @Reflejo indicates that optimized Envoy Mobile without symbols is observing ~20% improvement. Related to #10943 Risk level: Low Testing: bazel query deps to confirm no more v2 API deps. Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 53fca618e47702f6c8dbc323db9bd39d15725457
3 years ago
"//envoy/config/filter/network/rate_limit/v2:pkg",
"//envoy/config/filter/network/rbac/v2:pkg",
tools: API boosting support for renames. (#9442) The type database now has rename information. Also some misc. fixes for enum and generated static method handling support. Part of #8082 Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 2c8992bce1880ed7ae8ede837434b8713c24a615
5 years ago
"//envoy/config/filter/network/redis_proxy/v2:pkg",
"//envoy/config/filter/network/tcp_proxy/v2:pkg",
"//envoy/config/filter/network/thrift_proxy/v2alpha1:pkg",
api: remove v2 dependencies from v3 API protos. (#18817) This should reduce the binary size, which is particularly important for Envoy Mobile. Looking at a local opt build with debug symbols, I'm seeing a drop from ~400MB to ~380MB, so maybe 5% saving. @Reflejo indicates that optimized Envoy Mobile without symbols is observing ~20% improvement. Related to #10943 Risk level: Low Testing: bazel query deps to confirm no more v2 API deps. Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 53fca618e47702f6c8dbc323db9bd39d15725457
3 years ago
"//envoy/config/filter/thrift/rate_limit/v2alpha1:pkg",
tools: API boosting support for renames. (#9442) The type database now has rename information. Also some misc. fixes for enum and generated static method handling support. Part of #8082 Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 2c8992bce1880ed7ae8ede837434b8713c24a615
5 years ago
"//envoy/config/filter/thrift/router/v2alpha1:pkg",
"//envoy/config/health_checker/redis/v2:pkg",
"//envoy/config/listener/v2:pkg",
"//envoy/config/metrics/v2:pkg",
"//envoy/config/overload/v2alpha:pkg",
api: remove v2 dependencies from v3 API protos. (#18817) This should reduce the binary size, which is particularly important for Envoy Mobile. Looking at a local opt build with debug symbols, I'm seeing a drop from ~400MB to ~380MB, so maybe 5% saving. @Reflejo indicates that optimized Envoy Mobile without symbols is observing ~20% improvement. Related to #10943 Risk level: Low Testing: bazel query deps to confirm no more v2 API deps. Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 53fca618e47702f6c8dbc323db9bd39d15725457
3 years ago
"//envoy/config/ratelimit/v2:pkg",
"//envoy/config/rbac/v2:pkg",
tools: API boosting support for renames. (#9442) The type database now has rename information. Also some misc. fixes for enum and generated static method handling support. Part of #8082 Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 2c8992bce1880ed7ae8ede837434b8713c24a615
5 years ago
"//envoy/config/resource_monitor/fixed_heap/v2alpha:pkg",
"//envoy/config/resource_monitor/injected_resource/v2alpha:pkg",
xds: define empty config protos (#9581) Define empty config protos for all filters expecting google::protobuf::Empty Risk Level: medium (change of config type) Testing: unit Docs Changes: done Release Notes: define config protos for all extensions Co-authored-by: Derek Argueta <dereka@pinterest.com> Mirrored from https://github.com/envoyproxy/envoy @ 2d5a4e94720cc195324f79ca68f0e7a7dc83ee9e
5 years ago
"//envoy/config/retry/omit_canary_hosts/v2:pkg",
"//envoy/config/retry/previous_hosts/v2:pkg",
tools: API boosting support for renames. (#9442) The type database now has rename information. Also some misc. fixes for enum and generated static method handling support. Part of #8082 Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 2c8992bce1880ed7ae8ede837434b8713c24a615
5 years ago
"//envoy/config/trace/v2:pkg",
"//envoy/config/trace/v2alpha:pkg",
"//envoy/config/transport_socket/alts/v2alpha:pkg",
api: remove v2 dependencies from v3 API protos. (#18817) This should reduce the binary size, which is particularly important for Envoy Mobile. Looking at a local opt build with debug symbols, I'm seeing a drop from ~400MB to ~380MB, so maybe 5% saving. @Reflejo indicates that optimized Envoy Mobile without symbols is observing ~20% improvement. Related to #10943 Risk level: Low Testing: bazel query deps to confirm no more v2 API deps. Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 53fca618e47702f6c8dbc323db9bd39d15725457
3 years ago
"//envoy/config/transport_socket/tap/v2alpha:pkg",
tools: API boosting support for renames. (#9442) The type database now has rename information. Also some misc. fixes for enum and generated static method handling support. Part of #8082 Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 2c8992bce1880ed7ae8ede837434b8713c24a615
5 years ago
"//envoy/data/accesslog/v2:pkg",
"//envoy/data/tap/v2alpha:pkg",
api/docs: v3 API reference documentation. (#9719) This PR introduces a parallel v3 API reference documentation tree to the existing v2 one. The docs/root/api-v3/ tree was copied from docs/root/api-v2 and the necessary package path fixups were made manually. As a result, the tree largely resembles the v2 docs. Long term this is likely to evolve to reflect the shape of the new extensions tree. The message type, field and enum anchors are sed'ed to be distinct and self-consistent inside api-v3/. There were a number of API proto changes that were made to obtain a successful Sphinx build: * References to deprecated fields were replaced by references to the replacement field. * clang-format line wrapping in protoxform was removed, this breaks RST in some v3 protos. * Some packages (type/metadata/v2, data/cluster/v2alpha) were force upgraded to v3, to deal with references to types that are distinct in v2/v3. This is OK as these packages probably make sense to bump for v3, in general we're going to have to think about how to do this more cleanly, supporting dual v2/v3 references alongside each other. * Some evil hacks for field renaming added to migrate.py for RouteAction. There's also some additional machinery added to compute distinct v3/v3 build targets to point protodoc at. Risk level: Low Testing: Docs build, manual inspection. Fixes #8087 Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ ac88316892cd47b6a9b58e3736e20e8863cd0d27
5 years ago
"//envoy/service/accesslog/v2:pkg",
"//envoy/service/auth/v2:pkg",
"//envoy/service/discovery/v2:pkg",
"//envoy/service/load_stats/v2:pkg",
"//envoy/service/metrics/v2:pkg",
"//envoy/service/ratelimit/v2:pkg",
Add Client Status Discovery Service (CSDS) API definition (#9383) Add Client Status Discovery Service (CSDS) API definition. This can be used by debug tools to obtain config information for specific clients from control plane. Risk Level: Low Testing: N/A Signed-off-by: Fuqiang Gao <fuqianggao@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 10f756efa17e56c8d4d1033be7b4286410db4e01
5 years ago
"//envoy/service/status/v2:pkg",
api/docs: v3 API reference documentation. (#9719) This PR introduces a parallel v3 API reference documentation tree to the existing v2 one. The docs/root/api-v3/ tree was copied from docs/root/api-v2 and the necessary package path fixups were made manually. As a result, the tree largely resembles the v2 docs. Long term this is likely to evolve to reflect the shape of the new extensions tree. The message type, field and enum anchors are sed'ed to be distinct and self-consistent inside api-v3/. There were a number of API proto changes that were made to obtain a successful Sphinx build: * References to deprecated fields were replaced by references to the replacement field. * clang-format line wrapping in protoxform was removed, this breaks RST in some v3 protos. * Some packages (type/metadata/v2, data/cluster/v2alpha) were force upgraded to v3, to deal with references to types that are distinct in v2/v3. This is OK as these packages probably make sense to bump for v3, in general we're going to have to think about how to do this more cleanly, supporting dual v2/v3 references alongside each other. * Some evil hacks for field renaming added to migrate.py for RouteAction. There's also some additional machinery added to compute distinct v3/v3 build targets to point protodoc at. Risk level: Low Testing: Docs build, manual inspection. Fixes #8087 Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ ac88316892cd47b6a9b58e3736e20e8863cd0d27
5 years ago
"//envoy/service/tap/v2alpha:pkg",
"//envoy/type:pkg",
"//envoy/type/matcher:pkg",
"//envoy/type/metadata/v2:pkg",
"//envoy/type/tracing/v2:pkg",
],
)
proto_library(
name = "v3_protos",
visibility = ["//visibility:public"],
deps = [
dynamo: moving to contrib (#21715) Risk Level: low Testing: n/a Docs Changes: n/a Release Notes: inline Signed-off-by: Alyssa Wilk <alyssar@chromium.org> Mirrored from https://github.com/envoyproxy/envoy @ 352857fb678fd7063e82884d8b675b6cc816e563
2 years ago
"//contrib/envoy/extensions/filters/http/dynamo/v3:pkg",
filter: add language http filter "accept-language" (#20143) * filter: add language http filter "accept-language" Signed-off-by: ye1kiev4wohgho9s <a1ma5quahdial9hx@protonmail.com> Mirrored from https://github.com/envoyproxy/envoy @ 383ac2b4849bd2dac1ed330753dbecc2ad61e2d0
3 years ago
"//contrib/envoy/extensions/filters/http/language/v3alpha:pkg",
build: setup contrib (#17595) Signed-off-by: Matt Klein <mklein@lyft.com> Mirrored from https://github.com/envoyproxy/envoy @ e385e016e941b6c2d91096b0b792aa6940d4b38c
3 years ago
"//contrib/envoy/extensions/filters/http/squash/v3:pkg",
Add SXG filter extension (#17215) Filter to transform response to Signed HTTP Exchange (SXG) package using libsxg (https://github.com/google/libsxg). Signed-off-by: Chris Papazian <papazian@pinterest.com> Mirrored from https://github.com/envoyproxy/envoy @ 4aab7faa910e85c0832345c7113ff41859ba607d
3 years ago
"//contrib/envoy/extensions/filters/http/sxg/v3alpha:pkg",
client_ssl_auth: movig to contrib (#21742) Risk Level: low Testing: n/a Docs Changes: n/a Release Notes: inline Signed-off-by: Alyssa Wilk <alyssar@chromium.org> Mirrored from https://github.com/envoyproxy/envoy @ dc13401811e4a315b8443fc802683643ad9fd2eb
2 years ago
"//contrib/envoy/extensions/filters/network/client_ssl_auth/v3:pkg",
extension: added generic proxy network filter (#22826) * initial draft for the meta protocol proxy Signed-off-by: wbpcode <comems@msn.com> * minor update Signed-off-by: wbpcode <comems@msn.com> * add match implemented Signed-off-by: wbpcode <comems@msn.com> * add some simple test Signed-off-by: wbpcode <wbphub@live.com> * add more test for route matcher Signed-off-by: wbpcode <wbphub@live.com> * partial commit Signed-off-by: wbpcode <wbphub@live.com> * complete basic unit test Signed-off-by: wbpcode <comems@msn.com> * fix format Signed-off-by: wbpcode <comems@msn.com> * fix error after merge Signed-off-by: wbpcode <wbphub@live.com> * add some more test Signed-off-by: wbpcode <wbphub@live.com> * minor fix Signed-off-by: wbpcode <wangbaiping@corp.netease.com> * fix test Signed-off-by: wbpcode <wangbaiping@corp.netease.com> * just make it run Signed-off-by: wbpcode <wangbaiping@corp.netease.com> * just make it run Signed-off-by: wbpcode <wangbaiping@corp.netease.com> * first integration test Signed-off-by: wbpcode <wangbaiping@corp.netease.com> * complete almost all the tests and fix docs and format Signed-off-by: wbpcode <wangbaiping@corp.netease.com> * fix proto format Signed-off-by: wbpcode <wangbaiping@corp.netease.com> * minor update Signed-off-by: wbpcode <wangbaiping@corp.netease.com> * add cleanup Signed-off-by: wbpcode <wangbaiping@corp.netease.com> * update for clang tidy and type error Signed-off-by: wbpcode <wangbaiping@corp.netease.com> * lower coverage threshould Signed-off-by: wbpcode <wangbaiping@corp.netease.com> * fix unexpected include Signed-off-by: wbpcode <wangbaiping@corp.netease.com> * fix window build Signed-off-by: wbpcode <wangbaiping@corp.netease.com> * rename to generic proxy to avoid name conflict Signed-off-by: wbpcode <wangbaiping@corp.netease.com> * fix docs Signed-off-by: wbpcode <wangbaiping@corp.netease.com> * remove unnecessary readme Signed-off-by: wbpcode <wangbaiping@corp.netease.com> * update comments and name of matcher Signed-off-by: wbpcode <wangbaiping@corp.netease.com> * fix format Signed-off-by: wbpcode <wangbaiping@corp.netease.com> * add name method Signed-off-by: wbpcode <wangbaiping@corp.netease.com> * move everything to contrib Signed-off-by: wbpcode <wangbaiping@corp.netease.com> * simple release note Signed-off-by: wbpcode <wangbaiping@corp.netease.com> * fix format Signed-off-by: wbpcode <wangbaiping@corp.netease.com> Signed-off-by: wbpcode <comems@msn.com> Signed-off-by: wbpcode <wbphub@live.com> Signed-off-by: wbpcode <wangbaiping@corp.netease.com> Mirrored from https://github.com/envoyproxy/envoy @ 51c0d6f47c98087c7e3288205cbf8edf50ae0196
2 years ago
"//contrib/envoy/extensions/filters/network/generic_proxy/action/v3:pkg",
"//contrib/envoy/extensions/filters/network/generic_proxy/matcher/v3:pkg",
"//contrib/envoy/extensions/filters/network/generic_proxy/v3:pkg",
kafka broker filter: move to contrib (#17750) Part of https://github.com/envoyproxy/envoy/issues/14078 Signed-off-by: Matt Klein <mklein@lyft.com> Mirrored from https://github.com/envoyproxy/envoy @ 43311b95392c6216320b6f4125f094a773ced2b2
3 years ago
"//contrib/envoy/extensions/filters/network/kafka_broker/v3:pkg",
Kafka-mesh filter (#11936) Signed-off-by: Adam Kotwasinski <adam.kotwasinski@gmail.com> Mirrored from https://github.com/envoyproxy/envoy @ 0c8942dd82e3991d5162c4c53ec5b2e5c1d71010
3 years ago
"//contrib/envoy/extensions/filters/network/kafka_mesh/v3alpha:pkg",
contrib: move sql filters (#17800) Fixes https://github.com/envoyproxy/envoy/issues/14078 Signed-off-by: Matt Klein <mklein@lyft.com> Mirrored from https://github.com/envoyproxy/envoy @ ef82a02bed0e6ab3de45e87b365cb18b55be6010
3 years ago
"//contrib/envoy/extensions/filters/network/mysql_proxy/v3:pkg",
"//contrib/envoy/extensions/filters/network/postgres_proxy/v3alpha:pkg",
rocketmq: move to contrib (#17796) Part of https://github.com/envoyproxy/envoy/issues/14078 Signed-off-by: Matt Klein <mklein@lyft.com> Mirrored from https://github.com/envoyproxy/envoy @ 5b63ef4d5b8670977749a2f5a620d4b6d9f93a72
3 years ago
"//contrib/envoy/extensions/filters/network/rocketmq_proxy/v3:pkg",
sip_proxy: SIP protocol support in envoy (#18039) Signed-off-by: Mingling <mingling.ding01@gmail.com> Mirrored from https://github.com/envoyproxy/envoy @ dc1130d3de278b1e1da59899a6b802b7a0fa7b58
3 years ago
"//contrib/envoy/extensions/filters/network/sip_proxy/router/v3alpha:pkg",
Sipproxy update for routing affinity (#19254) Risk Level: Medium Testing: unit test & manual testing Docs Changes: update sip proxy docs Release Notes: Platform Specific Features: Signed-off-by: Mingling Ding <mingling.ding01@gmail.com> Co-authored-by: Felix Du <durd07@gmail.com> Mirrored from https://github.com/envoyproxy/envoy @ 7174c148a0763f2ed5863c3ab341d4a9ce01c54b
3 years ago
"//contrib/envoy/extensions/filters/network/sip_proxy/tra/v3alpha:pkg",
sip_proxy: SIP protocol support in envoy (#18039) Signed-off-by: Mingling <mingling.ding01@gmail.com> Mirrored from https://github.com/envoyproxy/envoy @ dc1130d3de278b1e1da59899a6b802b7a0fa7b58
3 years ago
"//contrib/envoy/extensions/filters/network/sip_proxy/v3alpha:pkg",
contrib: add Hyperscan matcher (#19473) Signed-off-by: Xie Zhihao <zhihao.xie@intel.com> Mirrored from https://github.com/envoyproxy/envoy @ 2572ce6de1a582547a30b59b40f0c614c713f03a
3 years ago
"//contrib/envoy/extensions/matching/input_matchers/hyperscan/v3alpha:pkg",
Listener: extend connection balancer (#20268) Signed-off-by: Loong Dai <loong.dai@intel.com> Mirrored from https://github.com/envoyproxy/envoy @ 2167cb3b0bc0353cf53bca4a14a846c19de59018
2 years ago
"//contrib/envoy/extensions/network/connection_balance/dlb/v3alpha:pkg",
Add CryptoMB private key provider to contrib. (#17826) Intel's IPP (Integrated Performance Primitives) crypto library has support for multi-buffer crypto operations. Briefly, multi-buffer cryptography is implemented with AVX-512 instructions using a SIMD (single instruction, multiple data) mechanism. Up to eight RSA or ECDSA operations are gathered together into a buffer and processed at the same time, providing potentially improved performance. The AVX-512 instructions are available on recently launched 3rd generation Xeon Scalable server processors (Ice Lake server) processors. This commit adds a private key provider to accelerate RSA and ECDSA crypto operations on recent Intel Xeon processors. Every worker thread has a queue of up-to-eight crypto operations. When the queue is full or when the timer is triggered, the queue is processed and all the pending handshakes are notified. The potential performance benefit depends on many factors: the size of the cpuset Envoy is running on, incoming traffic pattern, encryption type (RSA or ECDSA), and key size. In my own testing I saw the biggest performance increase when long RSA keys were used on an Envoy running in a fairly limited environment serving lots of new incoming TLS requests. For more details, see this Intel whitepaper which contains some more information about the AVX-512 instructions and potential performance increase: https://www.intel.com/content/www/us/en/architecture-and-technology/crypto-acceleration-in-xeon-scalable-processors-wp.html Additional Description: One new dependency is introduced: Intel’s ipp-crypto library. Currently the PR is using a development version of ipp-crypto because BoringSSL support is not yet part of any release. The ipp-crypto team has indicated that BoringSSL version will be included in future ipp-crypto releases. Basic tests are provided, and a fake library interface is included for testing on systems without the required AVX-512 instruction set. Risk Level: Medium (TLS security feature, not enabled by default) Testing: Unit tests Docs Changes: API interface is documented Release Notes: Added CryptoMB private key provider to contrib. Platform Specific Features: Requires Intel 3rd generation Xeon Scalable server processor for the AVX-512 IFMA instruction set. Fixes: #15871 Signed-off-by: Ismo Puustinen <ismo.puustinen@intel.com> Co-authored-by: Greg Greenway <ggreenway@apple.com> Mirrored from https://github.com/envoyproxy/envoy @ 2144166ca7a3f100ecae16700bc82920b2de4871
3 years ago
"//contrib/envoy/extensions/private_key_providers/cryptomb/v3alpha:pkg",
contrib: add QAT private key provider. (#21984) Next generation Intel® QAT support with Intel® Xeon® Scalable processors will feature an Intel® QAT cryptography and compression acceleration engine. QAT private key provider extension will use qatlib library (https://github.com/intel/qatlib) to accelerate RSA operations in handshakes. The extension will look a bit like the existing cryptomb private key provider. The use case is to move the expensive cryptographic operations away from the CPU to the accelerator device, leaving CPU cycles for other use. Support for Intel® QAT is already present in the mainline Linux kernel and in Kubernetes device plugins (to expose the device files to containers). There are previous generations of Intel QAT® hardware devices, but they are not supported by this extension. Signed-off-by: Ismo Puustinen <ismo.puustinen@intel.com> Mirrored from https://github.com/envoyproxy/envoy @ 9447ff5bfa8081fc2ddd5918b8ee9c1fd6720c7a
2 years ago
"//contrib/envoy/extensions/private_key_providers/qat/v3alpha:pkg",
contrib: add Hyperscan regex engine (#21973) Commit Message: contrib: add Hyperscan regex engine Additional Description: Hyperscan has been introduced as an input matcher earlier this year. Since the regex engine interface has been completed, the patch extent the usage of Hyperscan into a contrib regex engine. Risk Level: Low Testing: Unit Docs Changes: API Release Notes: N/A Platform Specific Features: Requires processor with SSSE3 support (nearly any modern x86 processor) Signed-off-by: Xie Zhihao <zhihao.xie@intel.com> Mirrored from https://github.com/envoyproxy/envoy @ 725d0b4b3e6fb84aa7dfd1ca4d5792f2dc4558b2
2 years ago
"//contrib/envoy/extensions/regex_engines/hyperscan/v3alpha:pkg",
contrib: add vcl socket interface extension (#18149) Signed-off-by: Florin Coras <fcoras@cisco.com> Mirrored from https://github.com/envoyproxy/envoy @ 41c62224bb476c2ee03a4e8d4d5855cc66db8b0f
3 years ago
"//contrib/envoy/extensions/vcl/v3alpha:pkg",
api/docs: v3 API reference documentation. (#9719) This PR introduces a parallel v3 API reference documentation tree to the existing v2 one. The docs/root/api-v3/ tree was copied from docs/root/api-v2 and the necessary package path fixups were made manually. As a result, the tree largely resembles the v2 docs. Long term this is likely to evolve to reflect the shape of the new extensions tree. The message type, field and enum anchors are sed'ed to be distinct and self-consistent inside api-v3/. There were a number of API proto changes that were made to obtain a successful Sphinx build: * References to deprecated fields were replaced by references to the replacement field. * clang-format line wrapping in protoxform was removed, this breaks RST in some v3 protos. * Some packages (type/metadata/v2, data/cluster/v2alpha) were force upgraded to v3, to deal with references to types that are distinct in v2/v3. This is OK as these packages probably make sense to bump for v3, in general we're going to have to think about how to do this more cleanly, supporting dual v2/v3 references alongside each other. * Some evil hacks for field renaming added to migrate.py for RouteAction. There's also some additional machinery added to compute distinct v3/v3 build targets to point protodoc at. Risk level: Low Testing: Docs build, manual inspection. Fixes #8087 Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ ac88316892cd47b6a9b58e3736e20e8863cd0d27
5 years ago
"//envoy/admin/v3:pkg",
"//envoy/config/accesslog/v3:pkg",
"//envoy/config/bootstrap/v3:pkg",
"//envoy/config/cluster/v3:pkg",
api: moving the k-v store to common (#18117) As discussed on #18034 Risk Level: medium Testing: n/a Docs Changes: n/a Release Notes: n/a Signed-off-by: Alyssa Wilk <alyssar@chromium.org> Mirrored from https://github.com/envoyproxy/envoy @ 41b22449badf5ac59a45db949c3a12006b0b7894
3 years ago
"//envoy/config/common/key_value/v3:pkg",
tap: factor out the TAP filter matcher for later reuse in other filters (#12429) This is the 1st PR for #11832 that factors out the TAP filter matcher to prepare for reuse in other filters. Signed-off-by: Yangmin Zhu <ymzhu@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 520389e677cdcd4a85df769deb40f6cdd2f4f6f8
4 years ago
"//envoy/config/common/matcher/v3:pkg",
ext_proc: Use the new mutation rules and new proto (#19622) Replace code in mutation_utils.cc with code that calls into the new mutation_rules library. Add the ability to keep a counter of failed header mutations, and also add the ability for an invalid mutation to cause the HTTP request to fail. Signed-off-by: Gregory Brail <gregbrail@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 1bea8aea1590ffab5bb185d32232f9bf265e6b1e
3 years ago
"//envoy/config/common/mutation_rules/v3:pkg",
api/docs: v3 API reference documentation. (#9719) This PR introduces a parallel v3 API reference documentation tree to the existing v2 one. The docs/root/api-v3/ tree was copied from docs/root/api-v2 and the necessary package path fixups were made manually. As a result, the tree largely resembles the v2 docs. Long term this is likely to evolve to reflect the shape of the new extensions tree. The message type, field and enum anchors are sed'ed to be distinct and self-consistent inside api-v3/. There were a number of API proto changes that were made to obtain a successful Sphinx build: * References to deprecated fields were replaced by references to the replacement field. * clang-format line wrapping in protoxform was removed, this breaks RST in some v3 protos. * Some packages (type/metadata/v2, data/cluster/v2alpha) were force upgraded to v3, to deal with references to types that are distinct in v2/v3. This is OK as these packages probably make sense to bump for v3, in general we're going to have to think about how to do this more cleanly, supporting dual v2/v3 references alongside each other. * Some evil hacks for field renaming added to migrate.py for RouteAction. There's also some additional machinery added to compute distinct v3/v3 build targets to point protodoc at. Risk level: Low Testing: Docs build, manual inspection. Fixes #8087 Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ ac88316892cd47b6a9b58e3736e20e8863cd0d27
5 years ago
"//envoy/config/core/v3:pkg",
"//envoy/config/endpoint/v3:pkg",
protos: Readd v2 legacy protos in v3 (#16338) Signed-off-by: Ryan Northey <ryan@synca.io> Mirrored from https://github.com/envoyproxy/envoy @ f06269d02cb36686a2a1db777a15b70bb3229e29
4 years ago
"//envoy/config/filter/thrift/router/v2alpha1:pkg",
api/docs: v3 API reference documentation. (#9719) This PR introduces a parallel v3 API reference documentation tree to the existing v2 one. The docs/root/api-v3/ tree was copied from docs/root/api-v2 and the necessary package path fixups were made manually. As a result, the tree largely resembles the v2 docs. Long term this is likely to evolve to reflect the shape of the new extensions tree. The message type, field and enum anchors are sed'ed to be distinct and self-consistent inside api-v3/. There were a number of API proto changes that were made to obtain a successful Sphinx build: * References to deprecated fields were replaced by references to the replacement field. * clang-format line wrapping in protoxform was removed, this breaks RST in some v3 protos. * Some packages (type/metadata/v2, data/cluster/v2alpha) were force upgraded to v3, to deal with references to types that are distinct in v2/v3. This is OK as these packages probably make sense to bump for v3, in general we're going to have to think about how to do this more cleanly, supporting dual v2/v3 references alongside each other. * Some evil hacks for field renaming added to migrate.py for RouteAction. There's also some additional machinery added to compute distinct v3/v3 build targets to point protodoc at. Risk level: Low Testing: Docs build, manual inspection. Fixes #8087 Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ ac88316892cd47b6a9b58e3736e20e8863cd0d27
5 years ago
"//envoy/config/grpc_credential/v3:pkg",
protos: Readd v2 legacy protos in v3 (#16338) Signed-off-by: Ryan Northey <ryan@synca.io> Mirrored from https://github.com/envoyproxy/envoy @ f06269d02cb36686a2a1db777a15b70bb3229e29
4 years ago
"//envoy/config/health_checker/redis/v2:pkg",
api/docs: v3 API reference documentation. (#9719) This PR introduces a parallel v3 API reference documentation tree to the existing v2 one. The docs/root/api-v3/ tree was copied from docs/root/api-v2 and the necessary package path fixups were made manually. As a result, the tree largely resembles the v2 docs. Long term this is likely to evolve to reflect the shape of the new extensions tree. The message type, field and enum anchors are sed'ed to be distinct and self-consistent inside api-v3/. There were a number of API proto changes that were made to obtain a successful Sphinx build: * References to deprecated fields were replaced by references to the replacement field. * clang-format line wrapping in protoxform was removed, this breaks RST in some v3 protos. * Some packages (type/metadata/v2, data/cluster/v2alpha) were force upgraded to v3, to deal with references to types that are distinct in v2/v3. This is OK as these packages probably make sense to bump for v3, in general we're going to have to think about how to do this more cleanly, supporting dual v2/v3 references alongside each other. * Some evil hacks for field renaming added to migrate.py for RouteAction. There's also some additional machinery added to compute distinct v3/v3 build targets to point protodoc at. Risk level: Low Testing: Docs build, manual inspection. Fixes #8087 Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ ac88316892cd47b6a9b58e3736e20e8863cd0d27
5 years ago
"//envoy/config/listener/v3:pkg",
"//envoy/config/metrics/v3:pkg",
"//envoy/config/overload/v3:pkg",
"//envoy/config/ratelimit/v3:pkg",
"//envoy/config/rbac/v3:pkg",
protos: Readd v2 legacy protos in v3 (#16338) Signed-off-by: Ryan Northey <ryan@synca.io> Mirrored from https://github.com/envoyproxy/envoy @ f06269d02cb36686a2a1db777a15b70bb3229e29
4 years ago
"//envoy/config/resource_monitor/fixed_heap/v2alpha:pkg",
"//envoy/config/resource_monitor/injected_resource/v2alpha:pkg",
"//envoy/config/retry/omit_canary_hosts/v2:pkg",
"//envoy/config/retry/previous_hosts/v2:pkg",
api/docs: v3 API reference documentation. (#9719) This PR introduces a parallel v3 API reference documentation tree to the existing v2 one. The docs/root/api-v3/ tree was copied from docs/root/api-v2 and the necessary package path fixups were made manually. As a result, the tree largely resembles the v2 docs. Long term this is likely to evolve to reflect the shape of the new extensions tree. The message type, field and enum anchors are sed'ed to be distinct and self-consistent inside api-v3/. There were a number of API proto changes that were made to obtain a successful Sphinx build: * References to deprecated fields were replaced by references to the replacement field. * clang-format line wrapping in protoxform was removed, this breaks RST in some v3 protos. * Some packages (type/metadata/v2, data/cluster/v2alpha) were force upgraded to v3, to deal with references to types that are distinct in v2/v3. This is OK as these packages probably make sense to bump for v3, in general we're going to have to think about how to do this more cleanly, supporting dual v2/v3 references alongside each other. * Some evil hacks for field renaming added to migrate.py for RouteAction. There's also some additional machinery added to compute distinct v3/v3 build targets to point protodoc at. Risk level: Low Testing: Docs build, manual inspection. Fixes #8087 Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ ac88316892cd47b6a9b58e3736e20e8863cd0d27
5 years ago
"//envoy/config/route/v3:pkg",
"//envoy/config/tap/v3:pkg",
"//envoy/config/trace/v3:pkg",
"//envoy/data/accesslog/v3:pkg",
"//envoy/data/cluster/v3:pkg",
"//envoy/data/core/v3:pkg",
dns_filter: Initial commit for dns_filter skeleton (#10376) This commit is this base structure and api definition for the DNS filter. The code itself takes no action on packets. Tests will be added later. Signed-off-by: Alvin Baptiste <alvinsb@gmail.com> Mirrored from https://github.com/envoyproxy/envoy @ b3949eaf2080809b8a3a6cf720eba2cfdf864472
5 years ago
"//envoy/data/dns/v3:pkg",
api: freeze v3 API. (#9694) In which we convert every v3alpha reference to v3. In future revs of the stable API versioning policy, we will develop better tooling to support > 2 alpha and stable versions. For v3, it seems reasonable to just mv v3alpha to v3, since there should be no external consumers yet. Risk level: Low Testing: bazel test //test/..., CI. Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 5248a4fb7d4c2a3d1fa151f944d3a63f6b7a06cf
5 years ago
"//envoy/data/tap/v3:pkg",
"//envoy/extensions/access_loggers/file/v3:pkg",
accesslogs: add CEL-based extension filter (#18363) This PR establishes the ability to filter access log production via CEL expressions over the set of Envoy attributes. This can simply the creation of Envoy access log filters, allowing complex tailoring. Risk Level: low Testing: unit Docs Changes: included Release Notes: updated Signed-off-by: Douglas Reid <douglas-reid@users.noreply.github.com> Mirrored from https://github.com/envoyproxy/envoy @ 77ca6cc0d9aaf0892aec3e2025fe2ad7cf0c39ff
3 years ago
"//envoy/extensions/access_loggers/filters/cel/v3:pkg",
api: freeze v3 API. (#9694) In which we convert every v3alpha reference to v3. In future revs of the stable API versioning policy, we will develop better tooling to support > 2 alpha and stable versions. For v3, it seems reasonable to just mv v3alpha to v3, since there should be no external consumers yet. Risk level: Low Testing: bazel test //test/..., CI. Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 5248a4fb7d4c2a3d1fa151f944d3a63f6b7a06cf
5 years ago
"//envoy/extensions/access_loggers/grpc/v3:pkg",
api: force migrate v3alpha -> v3 (#18392) Also adjust wip status for some things that are known to be used in production. Fixes https://github.com/envoyproxy/envoy/issues/17920 Signed-off-by: Matt Klein <mklein@lyft.com> Mirrored from https://github.com/envoyproxy/envoy @ 54b686bb5f16cae0d506293fbefb82ab5588c3d3
3 years ago
"//envoy/extensions/access_loggers/open_telemetry/v3:pkg",
Rename access log streams to make it more friendly to posix terminology (#15721) Signed-off-by: Sotiris Nanopoulos <sonanopo@microsoft.com> Mirrored from https://github.com/envoyproxy/envoy @ 98fb5d6f8fe09a88218598d757756e702857dd03
4 years ago
"//envoy/extensions/access_loggers/stream/v3:pkg",
Upstream Wasm proto from envoy-wasm. (#12159) Description: Upstream Wasm proto files from envoy-wasm. Risk Level: Low Testing: Unit tests in envoy-wasm, integration tests in istio/proxy. Docs Changes: N/A Release Notes: N/A Signed-off-by: John Plevyak <jplevyak@gmail.com> Mirrored from https://github.com/envoyproxy/envoy @ 26eaa2e85cee69e5c32ab6bf4c5ae3d338fa462f
4 years ago
"//envoy/extensions/access_loggers/wasm/v3:pkg",
bootstrap extension: internal listener (#19467) Signed-off-by: Yuchen Dai <silentdai@gmail.com> Mirrored from https://github.com/envoyproxy/envoy @ b34fcee23881be2e9d5b6e5f04ca6cba02ef4539
3 years ago
"//envoy/extensions/bootstrap/internal_listener/v3:pkg",
api: force migrate v3alpha -> v3 (#18392) Also adjust wip status for some things that are known to be used in production. Fixes https://github.com/envoyproxy/envoy/issues/17920 Signed-off-by: Matt Klein <mklein@lyft.com> Mirrored from https://github.com/envoyproxy/envoy @ 54b686bb5f16cae0d506293fbefb82ab5588c3d3
3 years ago
"//envoy/extensions/cache/simple_http_cache/v3:pkg",
api: freeze v3 API. (#9694) In which we convert every v3alpha reference to v3. In future revs of the stable API versioning policy, we will develop better tooling to support > 2 alpha and stable versions. For v3, it seems reasonable to just mv v3alpha to v3, since there should be no external consumers yet. Risk level: Low Testing: bazel test //test/..., CI. Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 5248a4fb7d4c2a3d1fa151f944d3a63f6b7a06cf
5 years ago
"//envoy/extensions/clusters/aggregate/v3:pkg",
"//envoy/extensions/clusters/dynamic_forward_proxy/v3:pkg",
"//envoy/extensions/clusters/redis/v3:pkg",
Add async_files library to support filesystem buffering and filesystem caching (#20332) Signed-off-by: Raven Black <ravenblack@dropbox.com> Mirrored from https://github.com/envoyproxy/envoy @ 18c779af9106a1d85203621c9f4453d5901744e8
3 years ago
"//envoy/extensions/common/async_files/v3:pkg",
api: freeze v3 API. (#9694) In which we convert every v3alpha reference to v3. In future revs of the stable API versioning policy, we will develop better tooling to support > 2 alpha and stable versions. For v3, it seems reasonable to just mv v3alpha to v3, since there should be no external consumers yet. Risk level: Low Testing: bazel test //test/..., CI. Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 5248a4fb7d4c2a3d1fa151f944d3a63f6b7a06cf
5 years ago
"//envoy/extensions/common/dynamic_forward_proxy/v3:pkg",
http: add support for skip filter match action (#14275) Adds support for associating a match tree with a HTTP filter, supporting a single "Skip" operation that will have the FM ignore the filter for the duration of the stream once matched. Signed-off-by: Snow Pettersen <snowp@lyft.com> Mirrored from https://github.com/envoyproxy/envoy @ 935a6598cd01324f03608ca77ebffc9608f7af81
4 years ago
"//envoy/extensions/common/matching/v3:pkg",
api: freeze v3 API. (#9694) In which we convert every v3alpha reference to v3. In future revs of the stable API versioning policy, we will develop better tooling to support > 2 alpha and stable versions. For v3, it seems reasonable to just mv v3alpha to v3, since there should be no external consumers yet. Risk level: Low Testing: bazel test //test/..., CI. Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 5248a4fb7d4c2a3d1fa151f944d3a63f6b7a06cf
5 years ago
"//envoy/extensions/common/ratelimit/v3:pkg",
"//envoy/extensions/common/tap/v3:pkg",
compression: add brotli compressor and decompressor (#12998) Commit Message: compression: add brotli compressor and decompressor Additional Description: Add new brotli compression extensions in addition to gzip. Risk Level: Low, no existing functionality is touched Testing: uni tests, manual tests with curl. Docs Changes: updated docs for compression and decompression HTTP filters to refer the new available encoder/decoder. Release Notes: updated current.rst Fixes #4429 The PR adds a new dependency on https://github.com/google/brotli. Here's the current criteria answers: | Criteria | Answer | |---------|---------| | Cloud Native Computing Foundation (CNCF) approved license | MIT | | Dependencies must not substantially increase the binary size unless they are optional | brotli's binary size built with `-c opt` is 752K | | No duplication of existing dependencies | no other dep provides Brotli | | Hosted on a git repository and the archive fetch must directly reference this repository. | https://github.com/google/brotli | | CVE history appears reasonable, no pathological CVE arcs | so far 4 CVEs related to brotli have been registered | | Code review (ideally PRs) before merge | PRs are reviewed before merge | | Security vulnerability process exists, with contact details and reporting/disclosure process | no policy exists, submitted https://github.com/google/brotli/issues/878 | | > 1 contributor responsible for a non-trivial number of commits | 75 contributors | | Tests run in CI | CI set up with AppVeyor and Github actions | | High test coverage (also static/dynamic analysis, fuzzing) | Fuzzers are run in CI | | Envoy can obtain advanced notification of vulnerabilities or of security releases | brotli is registered in CPE | | Do other significant projects have shared fate by using this dependency? | Google Chrome is using the library | | Releases (with release notes) | https://github.com/google/brotli/releases | | Commits/releases in last 90 days | last commit 9 days ago | Signed-off-by: Dmitry Rozhkov <dmitry.rozhkov@intel.com> Mirrored from https://github.com/envoyproxy/envoy @ 127aa55306c9e4366e10b3a6e26d01df826e2fc0
4 years ago
"//envoy/extensions/compression/brotli/compressor/v3:pkg",
"//envoy/extensions/compression/brotli/decompressor/v3:pkg",
compressor: expose generic compressor filter to users (#10553) Currently the generic HTTP compressor filter isn't exposed to users even though it's used internally by `envoy.filters.http.gzip` and can be used by external filter extensions. Expose the compressor's config API to users. For example the filter can be configured as follows: ... filter_chains: filters: - name: envoy.http_connection_manager config: http_filters: - name: envoy.filters.http.compressor config: disable_on_etag_header: true content_length: 100 content_type: - text/html - application/json compressor_library: name: envoy.filters.http.compressor.gzip config: memory_level: 3 window_bits: 10 compression_level: best compression_strategy: rle ... Multiple compressor filters using different compressor libraries, e.g. gzip and brotli, can be stacked in one filter chain. Signed-off-by: Dmitry Rozhkov <dmitry.rozhkov@linux.intel.com> Mirrored from https://github.com/envoyproxy/envoy @ 49efb9841a58ebdc43a666f55c445911c8e4181c
5 years ago
"//envoy/extensions/compression/gzip/compressor/v3:pkg",
compression: create a decompressor extensibility point and move gzip decompressor (#10744) creates decompressors as an extension point and moves the zlib based gzip decompressor. Signed-off-by: Jose Nino <jnino@lyft.com> Mirrored from https://github.com/envoyproxy/envoy @ 520e0c7050564ac7886129a87290e9e433470efd
5 years ago
"//envoy/extensions/compression/gzip/decompressor/v3:pkg",
compression: add zstd compressor and decompressor (#20434) Signed-off-by: rainingmaster <jinhua.tan@bytedance.com> Mirrored from https://github.com/envoyproxy/envoy @ 865595291a1de5397dda0de46dd6048a0d993ee6
3 years ago
"//envoy/extensions/compression/zstd/compressor/v3:pkg",
"//envoy/extensions/compression/zstd/decompressor/v3:pkg",
config: Adding config-validation interface, extension and CDS validator (#19857) * Adding custom config-validation interface, extension, and a CDS validator. Signed-off-by: Adi Suissa-Peleg <adip@google.com> Mirrored from https://github.com/envoyproxy/envoy @ e58c890ded5c13e60eba3285c96ffefd6f7215cf
3 years ago
"//envoy/extensions/config/validators/minimum_clusters/v3:pkg",
quic: upstream sends early data requests (#20167) Commit Message: make HTTP/3 upstream sends 0-RTT (early data) requests if it has cached 0-RTT credentials. Add a config knob in RouteAction to specify which request can be sent over early data, which by default are HTTP safe methods. Risk Level: high, changes to conn pool behavior though should only take effect for h3 pool Testing: added h3 upstream integration tests. Docs Changes: N/A Release Notes: changes to docs/root/version_history/current.rst Platform Specific Features: N/A Runtime guard: envoy.reloadable_features.http3_sends_early_data Fixes #18715, #19542 Signed-off-by: Dan Zhang <danzh@google.com> Signed-off-by: Dan Zhang <danzh@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 8ce13d75a982ddd347db5a333a4bb080922f7514
3 years ago
"//envoy/extensions/early_data/v3:pkg",
filters: Add dependencies.proto (#14750) Introduces the FilterDependency proto. This isn't quite an extension, but it's a common proto to be used by all filter extensions. Risk Level: Low (proto addition only) #14470 Signed-off-by: Auni Ahsan <auni@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 2da224f88afe5ec84ba802bd932f73ed13308a92
4 years ago
"//envoy/extensions/filters/common/dependency/v3:pkg",
api: freeze v3 API. (#9694) In which we convert every v3alpha reference to v3. In future revs of the stable API versioning policy, we will develop better tooling to support > 2 alpha and stable versions. For v3, it seems reasonable to just mv v3alpha to v3, since there should be no external consumers yet. Risk level: Low Testing: bazel test //test/..., CI. Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 5248a4fb7d4c2a3d1fa151f944d3a63f6b7a06cf
5 years ago
"//envoy/extensions/filters/common/fault/v3:pkg",
http: add support for skip filter match action (#14275) Adds support for associating a match tree with a HTTP filter, supporting a single "Skip" operation that will have the FM ignore the filter for the duration of the stream once matched. Signed-off-by: Snow Pettersen <snowp@lyft.com> Mirrored from https://github.com/envoyproxy/envoy @ 935a6598cd01324f03608ca77ebffc9608f7af81
4 years ago
"//envoy/extensions/filters/common/matcher/action/v3:pkg",
api: freeze v3 API. (#9694) In which we convert every v3alpha reference to v3. In future revs of the stable API versioning policy, we will develop better tooling to support > 2 alpha and stable versions. For v3, it seems reasonable to just mv v3alpha to v3, since there should be no external consumers yet. Risk level: Low Testing: bazel test //test/..., CI. Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 5248a4fb7d4c2a3d1fa151f944d3a63f6b7a06cf
5 years ago
"//envoy/extensions/filters/http/adaptive_concurrency/v3:pkg",
api: force migrate v3alpha -> v3 (#18392) Also adjust wip status for some things that are known to be used in production. Fixes https://github.com/envoyproxy/envoy/issues/17920 Signed-off-by: Matt Klein <mklein@lyft.com> Mirrored from https://github.com/envoyproxy/envoy @ 54b686bb5f16cae0d506293fbefb82ab5588c3d3
3 years ago
"//envoy/extensions/filters/http/admission_control/v3:pkg",
alternate_protocols_cache: Create a filter for parsing Alt-Svc headers and populating the AlternateProtocolsCache. (#16778) alternate_protocols_cache: Create a filter for parsing Alt-Svc headers and populating the AlternateProtocolsCache. Risk Level: Low Testing: Unit and Integration Docs Changes: N/A Release Notes: N/A Platform Specific Features: N/A Signed-off-by: Ryan Hamilton <rch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ e35a790bc3619fe304a3904ef81112db0a7e7b08
4 years ago
"//envoy/extensions/filters/http/alternate_protocols_cache/v3:pkg",
filter: AWS Lambda filter (initial version) (#10260) This filter transform HTTP requests to AWS Lambda invocations. The filter supports pass-through only. Meaning, the request body is passed to Lambda as is. Note: Lambda requires the request to be in JSON format. In a later iteration, we'll wrap the headers the body in a JSON string before passing it to Lambda. The filter requires the ARN of the Lambda function and supports per-filter-config. When the per-filter configuration is used, the target cluster must be tagged with specific metadata. This indicates to the filter whether to process the request or to skip it. Lambda supports two invocation modes: - Synchronous (Request-Response) - Asynchronous (Event) This initial version of the filter supports the synchronous mode only. In a later iteration I'll add support for the asynchronous (Event-based) version. Signed-off-by: Marco Magdy <mmagdy@gmail.com> Mirrored from https://github.com/envoyproxy/envoy @ 807401004d500899e9aa4c78fce007cf83b538cd
5 years ago
"//envoy/extensions/filters/http/aws_lambda/v3:pkg",
Add AWS request signing filter (#9751) This new alpha filter injects authentication headers for requests directed at AWS services that require authentication. Note: Requests over plain HTTP aren't handled yet, since the message body needs to be signed. Fixes #9708 Signed-off-by: Raul Gutierrez Segales <rgs@pinterest.com> Mirrored from https://github.com/envoyproxy/envoy @ ee2306673b79215641be02893cb4d8b2b256c466
5 years ago
"//envoy/extensions/filters/http/aws_request_signing/v3:pkg",
api: force migrate v3alpha -> v3 (#18392) Also adjust wip status for some things that are known to be used in production. Fixes https://github.com/envoyproxy/envoy/issues/17920 Signed-off-by: Matt Klein <mklein@lyft.com> Mirrored from https://github.com/envoyproxy/envoy @ 54b686bb5f16cae0d506293fbefb82ab5588c3d3
3 years ago
"//envoy/extensions/filters/http/bandwidth_limit/v3:pkg",
api: freeze v3 API. (#9694) In which we convert every v3alpha reference to v3. In future revs of the stable API versioning policy, we will develop better tooling to support > 2 alpha and stable versions. For v3, it seems reasonable to just mv v3alpha to v3, since there should be no external consumers yet. Risk level: Low Testing: bazel test //test/..., CI. Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 5248a4fb7d4c2a3d1fa151f944d3a63f6b7a06cf
5 years ago
"//envoy/extensions/filters/http/buffer/v3:pkg",
api: force migrate v3alpha -> v3 (#18392) Also adjust wip status for some things that are known to be used in production. Fixes https://github.com/envoyproxy/envoy/issues/17920 Signed-off-by: Matt Klein <mklein@lyft.com> Mirrored from https://github.com/envoyproxy/envoy @ 54b686bb5f16cae0d506293fbefb82ab5588c3d3
3 years ago
"//envoy/extensions/filters/http/cache/v3:pkg",
"//envoy/extensions/filters/http/cdn_loop/v3:pkg",
http: add composite filter allowing dynamic filter selection (#15198) Adds a new filter that makes use of the new matching API to allow specifying a filter configuration to use for specific match results. Once a configuration is selected, the desired filter is created and all callbacks delegated to the specific filter. Risk Level: Low, new filter Testing: IT + UT Docs Changes: Inline proto comments Signed-off-by: Snow Pettersen <snowp@lyft.com> Mirrored from https://github.com/envoyproxy/envoy @ d31ba23d494c310973ceaf1e053393697821e4d3
4 years ago
"//envoy/extensions/filters/http/composite/v3:pkg",
filters: add generic compressor filter (#7057) Signed-off-by: Dmitry Rozhkov <dmitry.rozhkov@linux.intel.com> Mirrored from https://github.com/envoyproxy/envoy @ 884bc7d13c06ca5c6f59e35ed0a8726b474e1d38
5 years ago
"//envoy/extensions/filters/http/compressor/v3:pkg",
api: freeze v3 API. (#9694) In which we convert every v3alpha reference to v3. In future revs of the stable API versioning policy, we will develop better tooling to support > 2 alpha and stable versions. For v3, it seems reasonable to just mv v3alpha to v3, since there should be no external consumers yet. Risk level: Low Testing: bazel test //test/..., CI. Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 5248a4fb7d4c2a3d1fa151f944d3a63f6b7a06cf
5 years ago
"//envoy/extensions/filters/http/cors/v3:pkg",
"//envoy/extensions/filters/http/csrf/v3:pkg",
compression: add generic decompressor filter (#11172) Commit Message: add generic decompressor filter Risk Level: low - low as it is an extension, med - for users as this is a brand new filter. Testing: unit tests, integration tests Docs Changes: added docs Release Notes: added release notes Signed-off-by: Jose Nino <jnino@lyft.com> Mirrored from https://github.com/envoyproxy/envoy @ 48a5b21d9483e7eddac79aeff7daac178d7b7462
5 years ago
"//envoy/extensions/filters/http/decompressor/v3:pkg",
api: freeze v3 API. (#9694) In which we convert every v3alpha reference to v3. In future revs of the stable API versioning policy, we will develop better tooling to support > 2 alpha and stable versions. For v3, it seems reasonable to just mv v3alpha to v3, since there should be no external consumers yet. Risk level: Low Testing: bazel test //test/..., CI. Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 5248a4fb7d4c2a3d1fa151f944d3a63f6b7a06cf
5 years ago
"//envoy/extensions/filters/http/dynamic_forward_proxy/v3:pkg",
"//envoy/extensions/filters/http/ext_authz/v3:pkg",
api: force migrate v3alpha -> v3 (#18392) Also adjust wip status for some things that are known to be used in production. Fixes https://github.com/envoyproxy/envoy/issues/17920 Signed-off-by: Matt Klein <mklein@lyft.com> Mirrored from https://github.com/envoyproxy/envoy @ 54b686bb5f16cae0d506293fbefb82ab5588c3d3
3 years ago
"//envoy/extensions/filters/http/ext_proc/v3:pkg",
api: freeze v3 API. (#9694) In which we convert every v3alpha reference to v3. In future revs of the stable API versioning policy, we will develop better tooling to support > 2 alpha and stable versions. For v3, it seems reasonable to just mv v3alpha to v3, since there should be no external consumers yet. Risk level: Low Testing: bazel test //test/..., CI. Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 5248a4fb7d4c2a3d1fa151f944d3a63f6b7a06cf
5 years ago
"//envoy/extensions/filters/http/fault/v3:pkg",
Add config proto for FileSystemBuffer filter (#20788) Signed-off-by: Raven Black <ravenblack@dropbox.com> Mirrored from https://github.com/envoyproxy/envoy @ a2776d8e86eb3d593976f0d0a8a941b7ee233184
3 years ago
"//envoy/extensions/filters/http/file_system_buffer/v3:pkg",
GCP Authentication Filter (#20112) * initial impl; basic framework Signed-off-by: Tianyu Xia <tyxia@google.com> Mirrored from https://github.com/envoyproxy/envoy @ c354e61f2f9823354bff08f3b11b8a13aa10ba78
3 years ago
"//envoy/extensions/filters/http/gcp_authn/v3:pkg",
api: freeze v3 API. (#9694) In which we convert every v3alpha reference to v3. In future revs of the stable API versioning policy, we will develop better tooling to support > 2 alpha and stable versions. For v3, it seems reasonable to just mv v3alpha to v3, since there should be no external consumers yet. Risk level: Low Testing: bazel test //test/..., CI. Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 5248a4fb7d4c2a3d1fa151f944d3a63f6b7a06cf
5 years ago
"//envoy/extensions/filters/http/grpc_http1_bridge/v3:pkg",
"//envoy/extensions/filters/http/grpc_http1_reverse_bridge/v3:pkg",
"//envoy/extensions/filters/http/grpc_json_transcoder/v3:pkg",
"//envoy/extensions/filters/http/grpc_stats/v3:pkg",
"//envoy/extensions/filters/http/grpc_web/v3:pkg",
"//envoy/extensions/filters/http/gzip/v3:pkg",
"//envoy/extensions/filters/http/header_to_metadata/v3:pkg",
"//envoy/extensions/filters/http/health_check/v3:pkg",
"//envoy/extensions/filters/http/ip_tagging/v3:pkg",
"//envoy/extensions/filters/http/jwt_authn/v3:pkg",
http: add Kill Request HTTP filter (#14170) Add a KillRequest HTTP filter which can crash Envoy when receiving a Kill request. It will be used to fault inject kill request to Envoy and measure the blast radius. Risk Level: Low, new feature. Testing: Unit/integration tests. Docs Changes: Added Release Notes: Added Issue: #13978 Signed-off-by: Qin Qin <qqin@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 237b29d6399953f22a47c6e4d19df74b4fbcee8d
4 years ago
"//envoy/extensions/filters/http/kill_request/v3:pkg",
Add HTTP local rate limiter (#13395) Signed-off-by: Raul Gutierrez Segales <rgs@pinterest.com> Mirrored from https://github.com/envoyproxy/envoy @ 5d12b675fe13747bc716859275c2d3c21004e99f
4 years ago
"//envoy/extensions/filters/http/local_ratelimit/v3:pkg",
api: freeze v3 API. (#9694) In which we convert every v3alpha reference to v3. In future revs of the stable API versioning policy, we will develop better tooling to support > 2 alpha and stable versions. For v3, it seems reasonable to just mv v3alpha to v3, since there should be no external consumers yet. Risk level: Low Testing: bazel test //test/..., CI. Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 5248a4fb7d4c2a3d1fa151f944d3a63f6b7a06cf
5 years ago
"//envoy/extensions/filters/http/lua/v3:pkg",
api: force migrate v3alpha -> v3 (#18392) Also adjust wip status for some things that are known to be used in production. Fixes https://github.com/envoyproxy/envoy/issues/17920 Signed-off-by: Matt Klein <mklein@lyft.com> Mirrored from https://github.com/envoyproxy/envoy @ 54b686bb5f16cae0d506293fbefb82ab5588c3d3
3 years ago
"//envoy/extensions/filters/http/oauth2/v3:pkg",
api: freeze v3 API. (#9694) In which we convert every v3alpha reference to v3. In future revs of the stable API versioning policy, we will develop better tooling to support > 2 alpha and stable versions. For v3, it seems reasonable to just mv v3alpha to v3, since there should be no external consumers yet. Risk level: Low Testing: bazel test //test/..., CI. Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 5248a4fb7d4c2a3d1fa151f944d3a63f6b7a06cf
5 years ago
"//envoy/extensions/filters/http/on_demand/v3:pkg",
"//envoy/extensions/filters/http/original_src/v3:pkg",
"//envoy/extensions/filters/http/ratelimit/v3:pkg",
"//envoy/extensions/filters/http/rbac/v3:pkg",
"//envoy/extensions/filters/http/router/v3:pkg",
Set-Metadata HTTP filter (#16400) This extension simply allows to add user-defined dynamic metadata. This is intended to be used with matchers, so that the "result" of a matching process can imply specific metadata. See issue #16266 Risk Level: Medium Testing: Unit tests for the extension are added Docs Changes: A small documentation for the extension is added in docs/root/configuration/http/http_filters Signed-off-by: Adrien Guinet <adrien@reblaze.com> Mirrored from https://github.com/envoyproxy/envoy @ cbe08bbe33005c1832964f7c9e657d6dbe105bbb
4 years ago
"//envoy/extensions/filters/http/set_metadata/v3:pkg",
extension: Add stateful session extension (#18207) Introduce a new stateful session extension. This is a change after #17848 #17290. In #17290, we added a new cross-priority host map for fast host searching. In #17848, we extend `LoadBalancerContext` interface to provide an override host and to select the upstream host by the override host. Finally, in this change, we expand a new API to allow users to extract the state of the session from the request and change the result of load balancing by setting the override host value. Related doc: https://docs.google.com/document/d/1IU4b76AgOXijNa4sew1gfBfSiOMbZNiEt5Dhis8QpYg/edit?usp=sharing. Risk Level: Medium Testing: Added Docs Changes: Added Release Notes: Added Platform-Specific Features: N/A. Signed-off-by: wbpcode <wbphub@live.com> Mirrored from https://github.com/envoyproxy/envoy @ fb2aad0303bbbcb0daabf6940c6ad97252995b98
3 years ago
"//envoy/extensions/filters/http/stateful_session/v3:pkg",
api: freeze v3 API. (#9694) In which we convert every v3alpha reference to v3. In future revs of the stable API versioning policy, we will develop better tooling to support > 2 alpha and stable versions. For v3, it seems reasonable to just mv v3alpha to v3, since there should be no external consumers yet. Risk level: Low Testing: bazel test //test/..., CI. Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 5248a4fb7d4c2a3d1fa151f944d3a63f6b7a06cf
5 years ago
"//envoy/extensions/filters/http/tap/v3:pkg",
http: cleaning upstream interfaces for upstream filters. (#22918) This changes the Upstream Filter code to creating the codec filter via factory which requires adding all UpstreamRequest/CodecFilter interactions to an UpstreamCallback interface accessible through the filter manager requires unhiding the configuration because the presubmit cross-checks for the registered factory require all the config be unhidden allows configuring the codec filter in configuration, in case of eventual alternate terminal filter allows fixing up the filter dependency validator to validate the entire upstream filter chain. Upstream filters flipped on for CI, SHOULD BE FLIPPED OFF BEFORE SUBMITTING Risk Level: low assuming it's flipped back off Testing: updated unit tests, covered by filter integration tests Docs Changes: n/a Release Notes: n/a (off by default) Part of #10455 Signed-off-by: Alyssa Wilk <alyssar@chromium.org> Mirrored from https://github.com/envoyproxy/envoy @ 978004308203aa9e86886512adf6b26376958405
2 years ago
"//envoy/extensions/filters/http/upstream_codec/v3:pkg",
Upstream Wasm proto from envoy-wasm. (#12159) Description: Upstream Wasm proto files from envoy-wasm. Risk Level: Low Testing: Unit tests in envoy-wasm, integration tests in istio/proxy. Docs Changes: N/A Release Notes: N/A Signed-off-by: John Plevyak <jplevyak@gmail.com> Mirrored from https://github.com/envoyproxy/envoy @ 26eaa2e85cee69e5c32ab6bf4c5ae3d338fa462f
4 years ago
"//envoy/extensions/filters/http/wasm/v3:pkg",
api: freeze v3 API. (#9694) In which we convert every v3alpha reference to v3. In future revs of the stable API versioning policy, we will develop better tooling to support > 2 alpha and stable versions. For v3, it seems reasonable to just mv v3alpha to v3, since there should be no external consumers yet. Risk level: Low Testing: bazel test //test/..., CI. Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 5248a4fb7d4c2a3d1fa151f944d3a63f6b7a06cf
5 years ago
"//envoy/extensions/filters/listener/http_inspector/v3:pkg",
"//envoy/extensions/filters/listener/original_dst/v3:pkg",
"//envoy/extensions/filters/listener/original_src/v3:pkg",
"//envoy/extensions/filters/listener/proxy_protocol/v3:pkg",
"//envoy/extensions/filters/listener/tls_inspector/v3:pkg",
Connection Limit Filter (#15519) Signed-off-by: delli <delli@microsoft.com> Mirrored from https://github.com/envoyproxy/envoy @ ce3b4da34a041c2946dd935524126d0743567466
3 years ago
"//envoy/extensions/filters/network/connection_limit/v3:pkg",
network: add direct response network filter (#10210) Signed-off-by: Kuat Yessenov <kuat@google.com> Mirrored from https://github.com/envoyproxy/envoy @ e8e20c3b045dcde43aee2f7eea63aa0d2b1edb2f
5 years ago
"//envoy/extensions/filters/network/direct_response/v3:pkg",
api: freeze v3 API. (#9694) In which we convert every v3alpha reference to v3. In future revs of the stable API versioning policy, we will develop better tooling to support > 2 alpha and stable versions. For v3, it seems reasonable to just mv v3alpha to v3, since there should be no external consumers yet. Risk level: Low Testing: bazel test //test/..., CI. Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 5248a4fb7d4c2a3d1fa151f944d3a63f6b7a06cf
5 years ago
"//envoy/extensions/filters/network/dubbo_proxy/router/v3:pkg",
"//envoy/extensions/filters/network/dubbo_proxy/v3:pkg",
"//envoy/extensions/filters/network/echo/v3:pkg",
"//envoy/extensions/filters/network/ext_authz/v3:pkg",
"//envoy/extensions/filters/network/http_connection_manager/v3:pkg",
"//envoy/extensions/filters/network/local_ratelimit/v3:pkg",
"//envoy/extensions/filters/network/mongo_proxy/v3:pkg",
"//envoy/extensions/filters/network/ratelimit/v3:pkg",
"//envoy/extensions/filters/network/rbac/v3:pkg",
"//envoy/extensions/filters/network/redis_proxy/v3:pkg",
"//envoy/extensions/filters/network/sni_cluster/v3:pkg",
api: force migrate v3alpha -> v3 (#18392) Also adjust wip status for some things that are known to be used in production. Fixes https://github.com/envoyproxy/envoy/issues/17920 Signed-off-by: Matt Klein <mklein@lyft.com> Mirrored from https://github.com/envoyproxy/envoy @ 54b686bb5f16cae0d506293fbefb82ab5588c3d3
3 years ago
"//envoy/extensions/filters/network/sni_dynamic_forward_proxy/v3:pkg",
api: freeze v3 API. (#9694) In which we convert every v3alpha reference to v3. In future revs of the stable API versioning policy, we will develop better tooling to support > 2 alpha and stable versions. For v3, it seems reasonable to just mv v3alpha to v3, since there should be no external consumers yet. Risk level: Low Testing: bazel test //test/..., CI. Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 5248a4fb7d4c2a3d1fa151f944d3a63f6b7a06cf
5 years ago
"//envoy/extensions/filters/network/tcp_proxy/v3:pkg",
thrift_proxy: Add thrift header to metadata filter (#18637) Signed-off-by: James Fish <jfish@pinterest.com> Mirrored from https://github.com/envoyproxy/envoy @ 6acc5d20cba6706cdba1c9ade2303f06061c88d9
3 years ago
"//envoy/extensions/filters/network/thrift_proxy/filters/header_to_metadata/v3:pkg",
api: freeze v3 API. (#9694) In which we convert every v3alpha reference to v3. In future revs of the stable API versioning policy, we will develop better tooling to support > 2 alpha and stable versions. For v3, it seems reasonable to just mv v3alpha to v3, since there should be no external consumers yet. Risk level: Low Testing: bazel test //test/..., CI. Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 5248a4fb7d4c2a3d1fa151f944d3a63f6b7a06cf
5 years ago
"//envoy/extensions/filters/network/thrift_proxy/filters/ratelimit/v3:pkg",
Migrate v2 thrift_filter to v3 api and corresponding docs changes. (#13885) part of #12841 Signed-off-by: Abhay Narayan Katare <abhay.katare@india.nec.com> Mirrored from https://github.com/envoyproxy/envoy @ 77d7cecb7e68cb41b2f5f7c2aa7f4294c88089ce
4 years ago
"//envoy/extensions/filters/network/thrift_proxy/router/v3:pkg",
api: freeze v3 API. (#9694) In which we convert every v3alpha reference to v3. In future revs of the stable API versioning policy, we will develop better tooling to support > 2 alpha and stable versions. For v3, it seems reasonable to just mv v3alpha to v3, since there should be no external consumers yet. Risk level: Low Testing: bazel test //test/..., CI. Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 5248a4fb7d4c2a3d1fa151f944d3a63f6b7a06cf
5 years ago
"//envoy/extensions/filters/network/thrift_proxy/v3:pkg",
Upstream Wasm proto from envoy-wasm. (#12159) Description: Upstream Wasm proto files from envoy-wasm. Risk Level: Low Testing: Unit tests in envoy-wasm, integration tests in istio/proxy. Docs Changes: N/A Release Notes: N/A Signed-off-by: John Plevyak <jplevyak@gmail.com> Mirrored from https://github.com/envoyproxy/envoy @ 26eaa2e85cee69e5c32ab6bf4c5ae3d338fa462f
4 years ago
"//envoy/extensions/filters/network/wasm/v3:pkg",
api: freeze v3 API. (#9694) In which we convert every v3alpha reference to v3. In future revs of the stable API versioning policy, we will develop better tooling to support > 2 alpha and stable versions. For v3, it seems reasonable to just mv v3alpha to v3, since there should be no external consumers yet. Risk level: Low Testing: bazel test //test/..., CI. Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 5248a4fb7d4c2a3d1fa151f944d3a63f6b7a06cf
5 years ago
"//envoy/extensions/filters/network/zookeeper_proxy/v3:pkg",
api: force migrate v3alpha -> v3 (#18392) Also adjust wip status for some things that are known to be used in production. Fixes https://github.com/envoyproxy/envoy/issues/17920 Signed-off-by: Matt Klein <mklein@lyft.com> Mirrored from https://github.com/envoyproxy/envoy @ 54b686bb5f16cae0d506293fbefb82ab5588c3d3
3 years ago
"//envoy/extensions/filters/udp/dns_filter/v3:pkg",
udp_proxy: upgrade to not alpha (#11339) This extension is used in production and we should treat it as such. Signed-off-by: Matt Klein <mklein@lyft.com> Mirrored from https://github.com/envoyproxy/envoy @ 86caf439d6cae2c8173b19fd4fdc95361565a72d
5 years ago
"//envoy/extensions/filters/udp/udp_proxy/v3:pkg",
access_log: metadata formatter extension (#17457) This PR addresses several issues: 1. MetadataFormatter base class takes a pointer to a function to access specific type of metadata. All other methods operating on internals of metadata structure are moved to base class. This simplified adding new types of metadata. 2. new type of access_log METADATA tag is introduced to handle all types of metadata. It is implemented as formatter extension. It handles existing tags DYNAMIC_METADATA and CLUSTER_METADATA, so two ways of accessing dynamic and cluster metadata are allowed now. Maybe we should obsolete DYNAMIC_METADATA and CLUSTER_METADATA in the future? 3. Adds handler for ROUTE metadata. See issue #3006. Follow up to #16121 Risk Level: Low Testing: Unit tests. Docs Changes: Yes. Release Notes: Yes. Platform Specific Features: No Signed-off-by: Christoph Pakulski <christoph@tetrate.io> Mirrored from https://github.com/envoyproxy/envoy @ 43b597e719230c8266998394301c5d0b3c862688
3 years ago
"//envoy/extensions/formatter/metadata/v3:pkg",
formatter: print request header without query string (#15711) Signed-off-by: Tero Saarni <tero.saarni@est.tech> Mirrored from https://github.com/envoyproxy/envoy @ 57366300c62f61664965f7d721059758e07f1216
3 years ago
"//envoy/extensions/formatter/req_without_query/v3:pkg",
extensions: update straggler v2 extensions to v3. (#14907) * Add v3 equivalents of v2 configs that were included in v3 due to no transitive deprecation. This increases consistency and reduces user confusion. We will continue to support these straggler v2 configs beyond the v2 turndown due to the late addition of v3 counterparts, special case code is added to utility.cc to handle this. * There were two extensions, //envoy/config/cluster/redis and //envoy/config/retry/previous_priorities, that for some reason were not upgraded to use v3 config. This is now fixed and I've grepped for other v2 in //source, none remain. Risk level: Medium (changes to extension config types and deprecated config handling). Testing: Additional unit test added for utility.cc handling, upgraded configs to v3 for other tests. Fixes #14735 Fixes #12841 Signed-off-by: Harvey Tuch <htuch@google.com> Co-authored-by: Abhay Narayan Katare <abhay.katare@india.nec.com> Mirrored from https://github.com/envoyproxy/envoy @ c04a75efe9d601ebcb9650f274b5adde60181f1c
4 years ago
"//envoy/extensions/health_checkers/redis/v3:pkg",
Thrift health checker support (#23043) Signed-off-by: kuochunghsu <kuochunghsu@pinterest.com> Mirrored from https://github.com/envoyproxy/envoy @ d079cb3b5cfc37f7f9c2d49e266c98d4a91b63e5
2 years ago
"//envoy/extensions/health_checkers/thrift/v3:pkg",
http: add HTTP/1.1 case preservation (#15619) 1) Add new stateful header formatter extension point 2) Add preserve case formatter extension Fixes https://github.com/envoyproxy/envoy/issues/14363 Signed-off-by: Matt Klein <mklein@lyft.com> Mirrored from https://github.com/envoyproxy/envoy @ 2a4d97ce66db565d191b42cdf51f4b99edf04f12
4 years ago
"//envoy/extensions/http/header_formatters/preserve_case/v3:pkg",
API for Unified Header Validators (#21172) API for Unified Header Validators Signed-off-by: Yan Avlasov <yavlasov@google.com> Mirrored from https://github.com/envoyproxy/envoy @ e569ce06101932cfe3ccb710c3c60b92dd09464b
3 years ago
"//envoy/extensions/http/header_validators/envoy_default/v3:pkg",
HCM: add support for IP detection extensions (#14855) This is a follow-up to: #14432 (comment) After that PR, it's no longer possible (unless you do a dynamic_cast) to set the remote address from a filter. This is something that we need to do because we have specialized logic for this (XFF doesn't work for us). So this adds an extension point which will allow us to push that logic down to ConnectionManagerUtility::mutateRequestHeaders() where it belongs. Signed-off-by: Raul Gutierrez Segales <rgs@pinterest.com> Mirrored from https://github.com/envoyproxy/envoy @ beac1ece7512e6e39b4f1c29490e247996a0f51c
4 years ago
"//envoy/extensions/http/original_ip_detection/custom_header/v3:pkg",
"//envoy/extensions/http/original_ip_detection/xff/v3:pkg",
extension: Add stateful session extension (#18207) Introduce a new stateful session extension. This is a change after #17848 #17290. In #17290, we added a new cross-priority host map for fast host searching. In #17848, we extend `LoadBalancerContext` interface to provide an override host and to select the upstream host by the override host. Finally, in this change, we expand a new API to allow users to extract the state of the session from the request and change the result of load balancing by setting the override host value. Related doc: https://docs.google.com/document/d/1IU4b76AgOXijNa4sew1gfBfSiOMbZNiEt5Dhis8QpYg/edit?usp=sharing. Risk Level: Medium Testing: Added Docs Changes: Added Release Notes: Added Platform-Specific Features: N/A. Signed-off-by: wbpcode <wbphub@live.com> Mirrored from https://github.com/envoyproxy/envoy @ fb2aad0303bbbcb0daabf6940c6ad97252995b98
3 years ago
"//envoy/extensions/http/stateful_session/cookie/v3:pkg",
stateful_session: add header based session state (#23145) * add the wireframe Signed-off-by: Pawan Bishnoi <pawanbishnoi@outlook.com> * Added bussiness logic. Working now Signed-off-by: Pawan Bishnoi <pawanbishnoi@outlook.com> * header name is read from config now instead of using a static one Signed-off-by: Pawan Bishnoi <pawanbishnoi@outlook.com> * fill more bussiness logic to achieve functional completeness Signed-off-by: Pawan Bishnoi <pawanbishnoi@outlook.com> * add unit and integration tests Signed-off-by: Pawan Bishnoi <pawanbishnoi@outlook.com> * added docs Signed-off-by: Pawan Bishnoi <pawanbishnoi@outlook.com> * add codeowners Signed-off-by: Pawan Bishnoi <pawanbishnoi@outlook.com> * remove header type inline the config instead Fix Intg test Signed-off-by: Pawan Bishnoi <pawanbishnoi@outlook.com> * remove path from HeaderBasedSessionState Signed-off-by: Pawan Bishnoi <pawanbishnoi@outlook.com> * fix build - attempt 1 Signed-off-by: Pawan Bishnoi <pawanbishnoi@outlook.com> * fix build - attempt 2 . Improve code coverage Signed-off-by: Pawan Bishnoi <pawanbishnoi@outlook.com> * improve doc format Signed-off-by: Pawan Bishnoi <pawanbishnoi@outlook.com> * retrigger CI to resolve a likely transient error Signed-off-by: Pawan Bishnoi <pawanbishnoi@outlook.com> * header replace instead of add. We have no usecase of keeping more than the value being set Signed-off-by: Pawan Bishnoi <pawanbishnoi@outlook.com> * address review comment to avoid unnecessary type conversion from string to HttpLowerCaseString Signed-off-by: Pawan Bishnoi <pawanbishnoi@outlook.com> * retrigger CI to resolve a likely transient error Signed-off-by: Pawan Bishnoi <pawanbishnoi@outlook.com> * review comments : avoid copy Signed-off-by: Pawan Bishnoi <pawanbishnoi@outlook.com> * add release note Signed-off-by: Pawan Bishnoi <pawanbishnoi@outlook.com> * remove extra newline Signed-off-by: Pawan Bishnoi <pawanbishnoi@outlook.com> * review comments. fix release note Signed-off-by: Pawan Bishnoi <pawanbishnoi@outlook.com> Signed-off-by: Pawan Bishnoi <pawanbishnoi@outlook.com> Mirrored from https://github.com/envoyproxy/envoy @ e2aa62acad2342cb7a84e8ad8d552e89d4c01b22
2 years ago
"//envoy/extensions/http/stateful_session/header/v3:pkg",
router: Create InternalRedirectPolicy in side RouteAction and extend it with pluggable predicates (#10908) Description: router: Create InternalRedirectPolicy to capture all internal redirect related options and extend it with pluggable predicates similar to retry plugins. The previous_routes and whitelisted_routes predicate allow creating a DAG of routes for internal redirects. Each node in the DAG is a route. whitelisted_routes defines the edges of each node. previous_routes serves as visited status keeper for each of the edge. This prevents infinite loop, while allowing loop to exist in the DAG. Risk Level: Medium Testing: Unit tests. Integration tests. Docs Changes: Updated HCM architecture overview page. Added toctree for the predicates. Release Notes: Updated version history. Signed-off-by: pengg <pengg@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 1ce010929d4d283fce977bc65558da71ffe6bf7c
5 years ago
"//envoy/extensions/internal_redirect/allow_listed_routes/v3:pkg",
"//envoy/extensions/internal_redirect/previous_routes/v3:pkg",
"//envoy/extensions/internal_redirect/safe_cross_scheme/v3:pkg",
dns: configuring a basic key value store to persist to disk (#17745) Risk Level: low (config guarded) Testing: new unit, integration tests Docs Changes: n/a (hidden) Release Notes: n/a Part of envoyproxy/envoy-mobile#1587 Signed-off-by: Alyssa Wilk <alyssar@chromium.org> Mirrored from https://github.com/envoyproxy/envoy @ 16879db8d6d3e859e169807e7b9510ba4b30501f
3 years ago
"//envoy/extensions/key_value/file_based/v3:pkg",
matching: add support for generic inputs and add environment variable input (#15410) Adds support for a "generic input" extension point that allows specifying inputs that are not dependent on protocol data. Adds an environment variable generic input that allows matching on the value of an environment variable. Signed-off-by: Snow Pettersen <snowp@lyft.com> Mirrored from https://github.com/envoyproxy/envoy @ 758a9a90c15331fbfd093f23170454c5a2fbf903
4 years ago
"//envoy/extensions/matching/common_inputs/environment_variable/v3:pkg",
matchers: add input types for network streams (#19493) Introduce data inputs for connection matching as part of #18871 Signed-off-by: Kuat Yessenov <kuat@google.com> Mirrored from https://github.com/envoyproxy/envoy @ a1181348a4f6df6011843a141814e28840d23eb5
3 years ago
"//envoy/extensions/matching/common_inputs/network/v3:pkg",
matching: add authenticated network input (#20916) Signed-off-by: Xie Zhihao <zhihao.xie@intel.com> Mirrored from https://github.com/envoyproxy/envoy @ c2b2816ead9aa3569ab3331b24606d55ac0bd8b3
2 years ago
"//envoy/extensions/matching/common_inputs/ssl/v3:pkg",
matching: introduce consistent hashing matcher (#14875) This introduces a new matcher that allows matching on an input value by computing a hash value and matching if the value % (configured value) is greater than a configured threshold. This is useful in being able to define match criteria that should match for a certain % of input values in a way that is consistent between independent Envoy instances (e.g. it does not rely on a random input). Risk Level: Low, new extension Testing: UTs Docs Changes: Inline proto docs Release Notes: n/a Platform Specific Features: n/a Fixes #14782 Signed-off-by: Snow Pettersen <snowp@lyft.com> Mirrored from https://github.com/envoyproxy/envoy @ 7fe3d358f7e7e4d4c7282d50c498a7ab0e759a36
4 years ago
"//envoy/extensions/matching/input_matchers/consistent_hashing/v3:pkg",
IP Matcher on a list of CIDR ranges (#16592) Input matcher that checks that an IP{v4,v6} belongs to a list of CIDR ranges Signed-off-by: Adrien Guinet <adrien@reblaze.com> Mirrored from https://github.com/envoyproxy/envoy @ 6cd6a0cab68c757c785e62e0d73d881f57c97839
3 years ago
"//envoy/extensions/matching/input_matchers/ip/v3:pkg",
Refactoring Envoy DNS resolution as extension (#17479) Signed-off-by: Yanjun Xiang <yanjunxiang@google.com> Mirrored from https://github.com/envoyproxy/envoy @ f4a88f969cfb58b36efcf649fc25e5c85e7e9f5c
3 years ago
"//envoy/extensions/network/dns_resolver/apple/v3:pkg",
"//envoy/extensions/network/dns_resolver/cares/v3:pkg",
dns: add a getaddrinfo based system resolver (#22080) This can be used when using the system resolver is desired. For example, on Android. Signed-off-by: Matt Klein <mklein@lyft.com> Mirrored from https://github.com/envoyproxy/envoy @ 516b3f304bccf451691224c71a357f9c62840b2b
2 years ago
"//envoy/extensions/network/dns_resolver/getaddrinfo/v3:pkg",
network: add socket interface factory and config option (#11630) Add bootstrap config option that allows startup injection of a custom SocketInterface. Risk Level: Low Testing: n/a Docs Changes: n/a Release Notes: n/a Signed-off-by: Florin Coras <fcoras@cisco.com> Mirrored from https://github.com/envoyproxy/envoy @ 13da8f415c372e7fde3b0105f58f57348e84acb5
4 years ago
"//envoy/extensions/network/socket_interface/v3:pkg",
Full Set Of Changes For Pattern Match and Rewrite (#22207) This PR will implement issue detailed here and described below: #7763 Match Patterns and Templates Wildcard support based on match patterns and templates. A match pattern matches an incoming URL path. Match patterns support glob operators to match URL text and variable definitions to bind matched text to names. Template patterns are used to re-write URLs. Template patterns build new URLs and may reference variables bound by a match pattern. Match Examples /**.m3u8 would match /foo.m3u8 and /foo/bar.m3u8. /{dir_name}/*.ts would match /example/file.ts and bind dir_name="example" for a later template match to use. /{dir_name}/**.ts would match /example/path/file.ts and bind dir_name="example" for a later template match to use. This would also match /example/.ts, which may or may not be a desired behavior. /{path=v1/*}/{file=*.ts} would match /v1/example/movie.ts (binding path="v1/example" and file="movie"), but would not match /v0/example/movie.ts. See post for full details and example: #7763 (comment) Risk Level: Testing: Unit tests. Both both internal matching/rewrite library and config/data plane changes. Signed-off-by: silverstar195 <seanmaloney@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 8cfc61f916cf52ce8bce6710686e9d4fca2c06bd
2 years ago
"//envoy/extensions/path/match/uri_template/v3:pkg",
"//envoy/extensions/path/rewrite/uri_template/v3:pkg",
quiche: make quic proof source and crypto stream pluggable (#16658) Commit Message: make quic proof source and crypto streams extensions. Add config for default ones. If not specified in config, the default ones will be used. Risk Level: low Testing: existing tests passed Part of #2557 Co-authored-by: Dan Zhang <danzh@google.com> Mirrored from https://github.com/envoyproxy/envoy @ beb5a93b08bd0c48a2a7dd2f40ca13bcdb0ed40e
4 years ago
"//envoy/extensions/quic/crypto_stream/v3:pkg",
"//envoy/extensions/quic/proof_source/v3:pkg",
rate limit: add computed descriptors (#14448) Signed-off-by: Kuat Yessenov <kuat@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 876a36368b0617b43977abfc37d2b5af05e7b1b2
4 years ago
"//envoy/extensions/rate_limit_descriptors/expr/v3:pkg",
rbac: add support for upstream ip policy. (#17645) Based on the dicsussion in the issue https://github.com/envoyproxy/envoy/issues/17410, this PR adds implementation for ability to add rbac policy to filter upstream ip addresses for dynamically resolved domains (by dynamic proxy filter). Signed-off-by: Jojy George Varghese <jojy_varghese@apple.com> Mirrored from https://github.com/envoyproxy/envoy @ 53f95570a7e9d7fa5414a4bc145852524fa017ed
3 years ago
"//envoy/extensions/rbac/matchers/upstream_ip_port/v3:pkg",
regex: add regex engine factory and config option (#21633) Add support for injecting regex engine with its options on startup in a bootstrap option. These are some API, runtime and implementation changes. * google_re2 in safe_regex will be deprecated and no longer be required. Regex::parseRegex will choose the registered regex engine to parse expressions into matchers. * A new bootstrap option default_regex_engine will be introduced for regex engine selection. * For compatibility, GoogleRE2 will be chosen as default regex engine if no regex engine is designated. Signed-off-by: Xie Zhihao <zhihao.xie@intel.com> Mirrored from https://github.com/envoyproxy/envoy @ 0a92cc86e7f8b88d5af0eb2e27b5c7ef64719e56
2 years ago
"//envoy/extensions/regex_engines/v3:pkg",
request_id: allow disabling trace reason packing (#15248) 1) Promote the default UUID request_id implementation to an actual extension that is required in the build and wire up all documentation. 2) Add a configuration option to the extension that allows trace reason packing to be disabled (the default continues to be for it to be enabled to match existing behavior). 3) Update all documentation for the new behavior. 4) Substantial cleanup of these code paths for clarity and robustness. Fixes https://github.com/envoyproxy/envoy/issues/11532 Signed-off-by: Matt Klein <mklein@lyft.com> Mirrored from https://github.com/envoyproxy/envoy @ 07c4c17be61c77d87d2c108b0775f2e606a7ae12
4 years ago
"//envoy/extensions/request_id/uuid/v3:pkg",
extensions: update straggler v2 extensions to v3. (#14907) * Add v3 equivalents of v2 configs that were included in v3 due to no transitive deprecation. This increases consistency and reduces user confusion. We will continue to support these straggler v2 configs beyond the v2 turndown due to the late addition of v3 counterparts, special case code is added to utility.cc to handle this. * There were two extensions, //envoy/config/cluster/redis and //envoy/config/retry/previous_priorities, that for some reason were not upgraded to use v3 config. This is now fixed and I've grepped for other v2 in //source, none remain. Risk level: Medium (changes to extension config types and deprecated config handling). Testing: Additional unit test added for utility.cc handling, upgraded configs to v3 for other tests. Fixes #14735 Fixes #12841 Signed-off-by: Harvey Tuch <htuch@google.com> Co-authored-by: Abhay Narayan Katare <abhay.katare@india.nec.com> Mirrored from https://github.com/envoyproxy/envoy @ c04a75efe9d601ebcb9650f274b5adde60181f1c
4 years ago
"//envoy/extensions/resource_monitors/fixed_heap/v3:pkg",
"//envoy/extensions/resource_monitors/injected_resource/v3:pkg",
"//envoy/extensions/retry/host/omit_canary_hosts/v3:pkg",
retry host predicate: add new predicate to omit hosts based on endpoint metadata match (#9563) Currently supported retry host predicates only allow omitting either previously tried or canary hosts. This enhancement is to add a new host predicate that looks at the endpoint metadata match and omits the host in case of a match with the host metadata. See #9531 Risk Level: Low Testing: Unit testing Docs Changes: Added new proto for omit_hosts Signed-off-by: Prakhar Gautam <prakhag@gmail.com> Mirrored from https://github.com/envoyproxy/envoy @ e2fdf70f0fca0f9a9a66046fd80b280981b3f0ed
5 years ago
"//envoy/extensions/retry/host/omit_host_metadata/v3:pkg",
extensions: update straggler v2 extensions to v3. (#14907) * Add v3 equivalents of v2 configs that were included in v3 due to no transitive deprecation. This increases consistency and reduces user confusion. We will continue to support these straggler v2 configs beyond the v2 turndown due to the late addition of v3 counterparts, special case code is added to utility.cc to handle this. * There were two extensions, //envoy/config/cluster/redis and //envoy/config/retry/previous_priorities, that for some reason were not upgraded to use v3 config. This is now fixed and I've grepped for other v2 in //source, none remain. Risk level: Medium (changes to extension config types and deprecated config handling). Testing: Additional unit test added for utility.cc handling, upgraded configs to v3 for other tests. Fixes #14735 Fixes #12841 Signed-off-by: Harvey Tuch <htuch@google.com> Co-authored-by: Abhay Narayan Katare <abhay.katare@india.nec.com> Mirrored from https://github.com/envoyproxy/envoy @ c04a75efe9d601ebcb9650f274b5adde60181f1c
4 years ago
"//envoy/extensions/retry/host/previous_hosts/v3:pkg",
api: freeze v3 API. (#9694) In which we convert every v3alpha reference to v3. In future revs of the stable API versioning policy, we will develop better tooling to support > 2 alpha and stable versions. For v3, it seems reasonable to just mv v3alpha to v3, since there should be no external consumers yet. Risk level: Low Testing: bazel test //test/..., CI. Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 5248a4fb7d4c2a3d1fa151f944d3a63f6b7a06cf
5 years ago
"//envoy/extensions/retry/priority/previous_priorities/v3:pkg",
extensions: Graphite stats sink (#16703) Signed-off-by: Pavel Fomin <mail@vaccarium.ru> Mirrored from https://github.com/envoyproxy/envoy @ a6f397fdb0deea94c4fea9aecd921e774834d623
3 years ago
"//envoy/extensions/stat_sinks/graphite_statsd/v3:pkg",
Upstream envoyproxy/envoy-wasm. (#12546) Signed-off-by: John Plevyak <jplevyak@gmail.com> Signed-off-by: Piotr Sikora <piotrsikora@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 319a9a647f19036d831a75f68350c90e98bfc365
4 years ago
"//envoy/extensions/stat_sinks/wasm/v3:pkg",
api: freeze v3 API. (#9694) In which we convert every v3alpha reference to v3. In future revs of the stable API versioning policy, we will develop better tooling to support > 2 alpha and stable versions. For v3, it seems reasonable to just mv v3alpha to v3, since there should be no external consumers yet. Risk level: Low Testing: bazel test //test/..., CI. Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 5248a4fb7d4c2a3d1fa151f944d3a63f6b7a06cf
5 years ago
"//envoy/extensions/transport_sockets/alts/v3:pkg",
Adding direct connect support. (#21942) Creates a transport socket for HTP/1.1 proxy support. With the combination of the transport socket, and a filter putting the proxy stream info in place this will redirect TCP connections to the proxy IP address prefix TLS connections with cleartext CONECT headers to the destination host, and strip CONNECT response change cleartext HTTP/1.1 to send fully qualified URLs Risk Level: medium (intended as a no op but it does have data plane refactory) Testing: new unit, integration tests Docs Changes: n/a Part of envoyproxy/envoy-mobile#1622 Signed-off-by: Alyssa Wilk <alyssar@chromium.org> Mirrored from https://github.com/envoyproxy/envoy @ 095f4ca336d3d705e629b207fb2cbbc22d29db8f
2 years ago
"//envoy/extensions/transport_sockets/http_11_proxy/v3:pkg",
transport sockets: support passthrough state for internal connections (#19435) Implements a special transport socket for transferring state (metadata and filter state) over the internal connection. This transport socket captures a subset of endpoint metadata, cluster metadata, and stream filter state in the user space socket. When an internal listener accepts a user space socket connection, it immediately merges this passthrough state into the connection stream info. Because the state can be transferred from HTTP stream to TCP stream, this transport socket also participates in the hashing decisions in the HTTP connection pools. Commit Message: Add passhtrough state over internal connection. Risk Level: low, new extension Testing: WIP Docs Changes: yes Release Notes: yes Platform Specific Features: Fixes: #19274 Signed-off-by: Kuat Yessenov <kuat@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 637a92a56e2739b5f78441c337171968f18b46ee
2 years ago
"//envoy/extensions/transport_sockets/internal_upstream/v3:pkg",
transport socket: Add proxy proto transport socket. (#11584) Commit Message: Add proxy proto transport socket Additional Description: This is the part 1 PR described in #10682. It adds the transports socket / unit tests, a transport socket options struct for the proxy proto header, and does a refactor to make the listener filter use the common proxy proto constants (potentially want to move these now since the proxy proto config api type is not in extensions?) Risk Level: Small Testing: Unit Docs Changes: None Release Notes: None Part Of: #1031 Signed-off-by: Weston Carlson <wez470@gmail.com> Co-authored-by: Lizan Zhou <lizan@tetrate.io> Mirrored from https://github.com/envoyproxy/envoy @ 8972b478e6c9f1e7342e3dbfb57b35317c0cc009
4 years ago
"//envoy/extensions/transport_sockets/proxy_protocol/v3:pkg",
quiche: update tar and implement EnvoyQuicProofSource (#11316) Signed-off-by: Dan Zhang <danzh@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 92e608f066b017d664d8fa161cfc735f0c6b41e7
5 years ago
"//envoy/extensions/transport_sockets/quic/v3:pkg",
api: freeze v3 API. (#9694) In which we convert every v3alpha reference to v3. In future revs of the stable API versioning policy, we will develop better tooling to support > 2 alpha and stable versions. For v3, it seems reasonable to just mv v3alpha to v3, since there should be no external consumers yet. Risk level: Low Testing: bazel test //test/..., CI. Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 5248a4fb7d4c2a3d1fa151f944d3a63f6b7a06cf
5 years ago
"//envoy/extensions/transport_sockets/raw_buffer/v3:pkg",
api: force migrate v3alpha -> v3 (#18392) Also adjust wip status for some things that are known to be used in production. Fixes https://github.com/envoyproxy/envoy/issues/17920 Signed-off-by: Matt Klein <mklein@lyft.com> Mirrored from https://github.com/envoyproxy/envoy @ 54b686bb5f16cae0d506293fbefb82ab5588c3d3
3 years ago
"//envoy/extensions/transport_sockets/s2a/v3:pkg",
transport socket: api and implementation for startTls transport socket (#13112) Signed-off-by: Christoph Pakulski <christoph@tetrate.io> Mirrored from https://github.com/envoyproxy/envoy @ 98e8bf3f09fa2af3735217bfc7046517250cdfd2
4 years ago
"//envoy/extensions/transport_sockets/starttls/v3:pkg",
api: freeze v3 API. (#9694) In which we convert every v3alpha reference to v3. In future revs of the stable API versioning policy, we will develop better tooling to support > 2 alpha and stable versions. For v3, it seems reasonable to just mv v3alpha to v3, since there should be no external consumers yet. Risk level: Low Testing: bazel test //test/..., CI. Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 5248a4fb7d4c2a3d1fa151f944d3a63f6b7a06cf
5 years ago
"//envoy/extensions/transport_sockets/tap/v3:pkg",
Add transport socket wrapper to collect OS-level TCP stats and export as envoy metrics (#17682) This adds a new transport socket wrapper for collecting OS-level TCP stats and publishing them as envoy metrics, in either the cluster or listener stats namespace (depending on upstream or downstream use). This allows attributing the TCP stats to specific listeners and clusters. Signed-off-by: Greg Greenway <ggreenway@apple.com> Mirrored from https://github.com/envoyproxy/envoy @ b959a46661ec87bba8268a1750506695125f2b06
3 years ago
"//envoy/extensions/transport_sockets/tcp_stats/v3:pkg",
api: freeze v3 API. (#9694) In which we convert every v3alpha reference to v3. In future revs of the stable API versioning policy, we will develop better tooling to support > 2 alpha and stable versions. For v3, it seems reasonable to just mv v3alpha to v3, since there should be no external consumers yet. Risk level: Low Testing: bazel test //test/..., CI. Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 5248a4fb7d4c2a3d1fa151f944d3a63f6b7a06cf
5 years ago
"//envoy/extensions/transport_sockets/tls/v3:pkg",
udp: Add a udp_packet_packet_writer_config option to UdpListenerConfig (#21241) udp: Add a udp_packet_packet_writer_config option to UdpListenerConfig. Fixes #21200 Risk Level: Low Testing: Existing and additional tests Docs Changes: None Release Notes: Added Platform Specific Features: N/A Signed-off-by: Ryan Hamilton <rch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 3a7b26aa3909488a8561a232b82845b8b4cd38bb
3 years ago
"//envoy/extensions/udp_packet_writer/v3:pkg",
upstreams: APIs, docs, and stubs for pluggable upstreams (#11554) split out from #11327 There's a bit of transitive ugliness: declaring the extensions requires security posture, requires stub build files, requires codeowners before the code move, but it'll be pretty short lived. Risk Level: Low (mostly only APIs) Testing: n/a Docs Changes: some of the new docs Release Notes: n/a Signed-off-by: Alyssa Wilk <alyssar@chromium.org> Mirrored from https://github.com/envoyproxy/envoy @ e8dc25ecec277c0b94d02151de79353a9ba07b4e
5 years ago
"//envoy/extensions/upstreams/http/generic/v3:pkg",
"//envoy/extensions/upstreams/http/http/v3:pkg",
"//envoy/extensions/upstreams/http/tcp/v3:pkg",
config: reworking HTTP upstream config (#14079) Replacing the http-protocol-specific fields in the cluster config with a new plugin Risk Level: medium Testing: updated tests to use the new config Docs Changes: updated docs to use the new config Release Notes: deprecation notes in the PR Deprecated: all http-specific cluster config. Signed-off-by: Alyssa Wilk <alyssar@chromium.org> Mirrored from https://github.com/envoyproxy/envoy @ 7554d61bccf136638bdfb383c10d049dc8bd3790
4 years ago
"//envoy/extensions/upstreams/http/v3:pkg",
conn_pool: making TCP upstreams pluggable (#13548) Risk Level: Medium (some refactory) Testing: existing tests pass Docs Changes: n/a Release Notes: n/a Fixes #13185 Signed-off-by: Alyssa Wilk <alyssar@chromium.org> Mirrored from https://github.com/envoyproxy/envoy @ 6a044a38b762214950aea40fcd0709cd7dccdc44
4 years ago
"//envoy/extensions/upstreams/tcp/generic/v3:pkg",
Proxy-WASM configuration protos. (#9256) Signed-off-by: John Plevyak <jplevyak@gmail.com> Mirrored from https://github.com/envoyproxy/envoy @ bd637c4e3d691a74721049bba5aacc4551123aa8
5 years ago
"//envoy/extensions/wasm/v3:pkg",
api: force migrate v3alpha -> v3 (#18392) Also adjust wip status for some things that are known to be used in production. Fixes https://github.com/envoyproxy/envoy/issues/17920 Signed-off-by: Matt Klein <mklein@lyft.com> Mirrored from https://github.com/envoyproxy/envoy @ 54b686bb5f16cae0d506293fbefb82ab5588c3d3
3 years ago
"//envoy/extensions/watchdog/profile_action/v3:pkg",
api: freeze v3 API. (#9694) In which we convert every v3alpha reference to v3. In future revs of the stable API versioning policy, we will develop better tooling to support > 2 alpha and stable versions. For v3, it seems reasonable to just mv v3alpha to v3, since there should be no external consumers yet. Risk level: Low Testing: bazel test //test/..., CI. Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 5248a4fb7d4c2a3d1fa151f944d3a63f6b7a06cf
5 years ago
"//envoy/service/accesslog/v3:pkg",
"//envoy/service/auth/v3:pkg",
"//envoy/service/cluster/v3:pkg",
"//envoy/service/discovery/v3:pkg",
"//envoy/service/endpoint/v3:pkg",
API definitions for health check & outlier detection event services (#10407) This PR introduces gRPC services interfaces for outlier detection and healthcheck events services. Risk Level: low Testing: n.a. Docs Changes: not yet Release Notes: not yet Relates to #8970 Signed-off-by: Alexey Baranov <me@kotiki.cc> Mirrored from https://github.com/envoyproxy/envoy @ 34fcdef99633947543070d5eadf32867e940694e
5 years ago
"//envoy/service/event_reporting/v3:pkg",
api: force migrate v3alpha -> v3 (#18392) Also adjust wip status for some things that are known to be used in production. Fixes https://github.com/envoyproxy/envoy/issues/17920 Signed-off-by: Matt Klein <mklein@lyft.com> Mirrored from https://github.com/envoyproxy/envoy @ 54b686bb5f16cae0d506293fbefb82ab5588c3d3
3 years ago
"//envoy/service/ext_proc/v3:pkg",
xds: implement extension config discovery for HCM (#11826) Signed-off-by: Kuat Yessenov <kuat@google.com> Mirrored from https://github.com/envoyproxy/envoy @ e8216a8cf79c54e3e0a77ab729ebf27f4e79eb1b
4 years ago
"//envoy/service/extension/v3:pkg",
api: freeze v3 API. (#9694) In which we convert every v3alpha reference to v3. In future revs of the stable API versioning policy, we will develop better tooling to support > 2 alpha and stable versions. For v3, it seems reasonable to just mv v3alpha to v3, since there should be no external consumers yet. Risk level: Low Testing: bazel test //test/..., CI. Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 5248a4fb7d4c2a3d1fa151f944d3a63f6b7a06cf
5 years ago
"//envoy/service/health/v3:pkg",
"//envoy/service/listener/v3:pkg",
"//envoy/service/load_stats/v3:pkg",
"//envoy/service/metrics/v3:pkg",
"//envoy/service/ratelimit/v3:pkg",
"//envoy/service/route/v3:pkg",
"//envoy/service/runtime/v3:pkg",
"//envoy/service/secret/v3:pkg",
Add Client Status Discovery Service (CSDS) API definition (#9383) Add Client Status Discovery Service (CSDS) API definition. This can be used by debug tools to obtain config information for specific clients from control plane. Risk Level: Low Testing: N/A Signed-off-by: Fuqiang Gao <fuqianggao@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 10f756efa17e56c8d4d1033be7b4286410db4e01
5 years ago
"//envoy/service/status/v3:pkg",
api: freeze v3 API. (#9694) In which we convert every v3alpha reference to v3. In future revs of the stable API versioning policy, we will develop better tooling to support > 2 alpha and stable versions. For v3, it seems reasonable to just mv v3alpha to v3, since there should be no external consumers yet. Risk level: Low Testing: bazel test //test/..., CI. Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 5248a4fb7d4c2a3d1fa151f944d3a63f6b7a06cf
5 years ago
"//envoy/service/tap/v3:pkg",
"//envoy/service/trace/v3:pkg",
[http] API changes to split path header normalization and forwarding (#15044) * Configuration for path normalization so that normalization can be configured for internal only use and/or forwarding. Signed-off-by: Asra Ali <asraa@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 236107df5d15381ccf5040c0cb0f163ece9627a2
4 years ago
"//envoy/type/http/v3:pkg",
api: freeze v3 API. (#9694) In which we convert every v3alpha reference to v3. In future revs of the stable API versioning policy, we will develop better tooling to support > 2 alpha and stable versions. For v3, it seems reasonable to just mv v3alpha to v3, since there should be no external consumers yet. Risk level: Low Testing: bazel test //test/..., CI. Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 5248a4fb7d4c2a3d1fa151f944d3a63f6b7a06cf
5 years ago
"//envoy/type/matcher/v3:pkg",
api/docs: v3 API reference documentation. (#9719) This PR introduces a parallel v3 API reference documentation tree to the existing v2 one. The docs/root/api-v3/ tree was copied from docs/root/api-v2 and the necessary package path fixups were made manually. As a result, the tree largely resembles the v2 docs. Long term this is likely to evolve to reflect the shape of the new extensions tree. The message type, field and enum anchors are sed'ed to be distinct and self-consistent inside api-v3/. There were a number of API proto changes that were made to obtain a successful Sphinx build: * References to deprecated fields were replaced by references to the replacement field. * clang-format line wrapping in protoxform was removed, this breaks RST in some v3 protos. * Some packages (type/metadata/v2, data/cluster/v2alpha) were force upgraded to v3, to deal with references to types that are distinct in v2/v3. This is OK as these packages probably make sense to bump for v3, in general we're going to have to think about how to do this more cleanly, supporting dual v2/v3 references alongside each other. * Some evil hacks for field renaming added to migrate.py for RouteAction. There's also some additional machinery added to compute distinct v3/v3 build targets to point protodoc at. Risk level: Low Testing: Docs build, manual inspection. Fixes #8087 Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ ac88316892cd47b6a9b58e3736e20e8863cd0d27
5 years ago
"//envoy/type/metadata/v3:pkg",
"//envoy/type/tracing/v3:pkg",
api: freeze v3 API. (#9694) In which we convert every v3alpha reference to v3. In future revs of the stable API versioning policy, we will develop better tooling to support > 2 alpha and stable versions. For v3, it seems reasonable to just mv v3alpha to v3, since there should be no external consumers yet. Risk level: Low Testing: bazel test //test/..., CI. Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 5248a4fb7d4c2a3d1fa151f944d3a63f6b7a06cf
5 years ago
"//envoy/type/v3:pkg",
api: force migrate v3alpha -> v3 (#18392) Also adjust wip status for some things that are known to be used in production. Fixes https://github.com/envoyproxy/envoy/issues/17920 Signed-off-by: Matt Klein <mklein@lyft.com> Mirrored from https://github.com/envoyproxy/envoy @ 54b686bb5f16cae0d506293fbefb82ab5588c3d3
3 years ago
"//envoy/watchdog/v3:pkg",
tools: API boosting support for renames. (#9442) The type database now has rename information. Also some misc. fixes for enum and generated static method handling support. Part of #8082 Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 2c8992bce1880ed7ae8ede837434b8713c24a615
5 years ago
],
)
api/docs: v3 API reference documentation. (#9719) This PR introduces a parallel v3 API reference documentation tree to the existing v2 one. The docs/root/api-v3/ tree was copied from docs/root/api-v2 and the necessary package path fixups were made manually. As a result, the tree largely resembles the v2 docs. Long term this is likely to evolve to reflect the shape of the new extensions tree. The message type, field and enum anchors are sed'ed to be distinct and self-consistent inside api-v3/. There were a number of API proto changes that were made to obtain a successful Sphinx build: * References to deprecated fields were replaced by references to the replacement field. * clang-format line wrapping in protoxform was removed, this breaks RST in some v3 protos. * Some packages (type/metadata/v2, data/cluster/v2alpha) were force upgraded to v3, to deal with references to types that are distinct in v2/v3. This is OK as these packages probably make sense to bump for v3, in general we're going to have to think about how to do this more cleanly, supporting dual v2/v3 references alongside each other. * Some evil hacks for field renaming added to migrate.py for RouteAction. There's also some additional machinery added to compute distinct v3/v3 build targets to point protodoc at. Risk level: Low Testing: Docs build, manual inspection. Fixes #8087 Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ ac88316892cd47b6a9b58e3736e20e8863cd0d27
5 years ago
docs: add cncf/xds protos (#20277) Signed-off-by: Kuat Yessenov <kuat@google.com> Mirrored from https://github.com/envoyproxy/envoy @ c39f2b2e951a5059d16c84b4786cc0de22d4f002
3 years ago
proto_library(
name = "xds_protos",
visibility = ["//visibility:public"],
deps = [
"@com_github_cncf_udpa//xds/core/v3:pkg",
"@com_github_cncf_udpa//xds/type/matcher/v3:pkg",
"@com_github_cncf_udpa//xds/type/v3:pkg",
],
)
api/docs: v3 API reference documentation. (#9719) This PR introduces a parallel v3 API reference documentation tree to the existing v2 one. The docs/root/api-v3/ tree was copied from docs/root/api-v2 and the necessary package path fixups were made manually. As a result, the tree largely resembles the v2 docs. Long term this is likely to evolve to reflect the shape of the new extensions tree. The message type, field and enum anchors are sed'ed to be distinct and self-consistent inside api-v3/. There were a number of API proto changes that were made to obtain a successful Sphinx build: * References to deprecated fields were replaced by references to the replacement field. * clang-format line wrapping in protoxform was removed, this breaks RST in some v3 protos. * Some packages (type/metadata/v2, data/cluster/v2alpha) were force upgraded to v3, to deal with references to types that are distinct in v2/v3. This is OK as these packages probably make sense to bump for v3, in general we're going to have to think about how to do this more cleanly, supporting dual v2/v3 references alongside each other. * Some evil hacks for field renaming added to migrate.py for RouteAction. There's also some additional machinery added to compute distinct v3/v3 build targets to point protodoc at. Risk level: Low Testing: Docs build, manual inspection. Fixes #8087 Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ ac88316892cd47b6a9b58e3736e20e8863cd0d27
5 years ago
proto_library(
name = "all_protos",
visibility = ["//visibility:public"],
deps = [
":v2_protos",
":v3_protos",
docs: add cncf/xds protos (#20277) Signed-off-by: Kuat Yessenov <kuat@google.com> Mirrored from https://github.com/envoyproxy/envoy @ c39f2b2e951a5059d16c84b4786cc0de22d4f002
3 years ago
":xds_protos",
api/docs: v3 API reference documentation. (#9719) This PR introduces a parallel v3 API reference documentation tree to the existing v2 one. The docs/root/api-v3/ tree was copied from docs/root/api-v2 and the necessary package path fixups were made manually. As a result, the tree largely resembles the v2 docs. Long term this is likely to evolve to reflect the shape of the new extensions tree. The message type, field and enum anchors are sed'ed to be distinct and self-consistent inside api-v3/. There were a number of API proto changes that were made to obtain a successful Sphinx build: * References to deprecated fields were replaced by references to the replacement field. * clang-format line wrapping in protoxform was removed, this breaks RST in some v3 protos. * Some packages (type/metadata/v2, data/cluster/v2alpha) were force upgraded to v3, to deal with references to types that are distinct in v2/v3. This is OK as these packages probably make sense to bump for v3, in general we're going to have to think about how to do this more cleanly, supporting dual v2/v3 references alongside each other. * Some evil hacks for field renaming added to migrate.py for RouteAction. There's also some additional machinery added to compute distinct v3/v3 build targets to point protodoc at. Risk level: Low Testing: Docs build, manual inspection. Fixes #8087 Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ ac88316892cd47b6a9b58e3736e20e8863cd0d27
5 years ago
],
)
ci: Add API protobuf breaking-change-detector CI script (#17793) This PR is a continuation to #17515 - it adds a script that uses buf to check for breaking changes on proto files in the api folder. It does so by comparing the current api folder against the api folder at the git commit computed by tools/git/last_github_commit.sh - that should hopefully represent the most recent commit on main (if there is a better method to obtain the base branch commit, let me know!). Adding the script also required re-organizing some of the breaking change detector logic from the previous pr: some levels of abstraction were added, and the detector now expects a git repository and ref as the input for initial state (rather than a proto file). The script is invoked in do_ci.sh if bazel.api_compat is specified as the CI_TARGET. This PR also bumps the buf bazel dependency to 0.53.0. If this is preferred to be in a separate PR, let me know and I would be happy to do so Risk Level: low (hopefully) - the CI script will be invoked in a separate CI pipeline job that can be set to be optional on github. The azure pipeline has been added but needs to be set to optional by a CI maintainer Testing: New scripts and logic were tested manually; also ran tests from the previous PR and they still pass. hoping to observe more output of this tool through reading CI logs of other PRs once this is merged (this PR should not affect the existing PR workflow - refer to Risk Level) Docs Changes: n/a Release Notes: n/a Platform Specific Features: CI script uses a linux binary for buf so it cannot be run outside of docker on non-linux systems Fixes #3368 Signed-off-by: Yaseen Alkhafaji <yaseena@google.com> Mirrored from https://github.com/envoyproxy/envoy @ f30c289e456df11d549d7236c56f22da00500e9e
3 years ago
filegroup(
name = "proto_breaking_change_detector_buf_config",
srcs = [
"buf.yaml",
],
visibility = ["//visibility:public"],
)
tooling: Optimize `config_validation` (#21607) Signed-off-by: Ryan Northey <ryan@synca.io> Mirrored from https://github.com/envoyproxy/envoy @ 2b2a08b23611a7a77942e1a203b24a0ebb1698df
2 years ago
proto_descriptor_set(
name = "v3_proto_set",
visibility = ["//visibility:public"],
deps = [
":v3_protos",
":xds_protos",
],
)