[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.

Tag: Branch: Tree: 3db6a0f841

main

master-ci-test

Branches Tags

${ item.name }

Create tag ${ searchTerm }

Create branch ${ searchTerm }

from '3db6a0f841'

${ noResults }

data-plane-api/envoy/config/route

History

data-plane-api(Azure Pipelines) 77872e2bb4 [API] Allow routing to the cluster specified in the request_header for weighted cluster case. (#17673) ... - Add cluster header to weighted cluster proto. This enables the ability of routing to the cluster specified in the request_header for weighted cluster (i.e. multiple upstreams) case. name and cluster_header will be oneof cluster_specifiter field in the next release. Currently, they can only be regular fields due to compatibility issue. - Add the validation logic (PGV annotation + runtime check) - Add 3 unit tests for invalid weighted cluster configs. Note: I have implemented the core implementation and tested it with end-to-end integration test/example locally. Those changes will be in a separate PR once this API change is approved. Risk Level: Low Testing: CI, added an integration test for implementation of this API locally Signed-off-by: Tianyu Xia <tyxia@google.com> Mirrored from https://github.com/envoyproxy/envoy @ ef70185f3ac241d09eabfe15c65b0d631134f74f		4 years ago
..
v3	[API] Allow routing to the cluster specified in the request_header for weighted cluster case. (#17673)	4 years ago