From 639e9b9c5f90c5b8394a4650cb453b476ade8454 Mon Sep 17 00:00:00 2001 From: Stephan Zuercher Date: Thu, 28 Sep 2017 10:56:37 -0700 Subject: [PATCH] cds: rename field, update comments to match design choices Signed-off-by: Stephan Zuercher --- api/cds.proto | 12 +++++------- 1 file changed, 5 insertions(+), 7 deletions(-) diff --git a/api/cds.proto b/api/cds.proto index 596cf786b..6842e78a7 100644 --- a/api/cds.proto +++ b/api/cds.proto @@ -259,19 +259,17 @@ message Cluster { // Specifications for subsets. For each entry, LbEndpoint.Metadata's // "envoy.lb" namespace is traversed and a subset is created for each unique // combination of key and value. For example: - // { "subset_keys": [ + // { "subset_selectors": [ // { "keys": [ "version" ] }, // { "keys": [ "stage", "hardware_type" ] } // ]} // A subset is matched when the metadata from the selected route and - // weighted cluster contains the keys and values from the subset's - // metadata. Extra keys in the route metadata are ignored when comparing the - // subset's metadata. Subsets may overlap. In the case of overlapping - // subsets, the first matching subset is selected. - message LbSubsetKeys { + // weighted cluster contains the same keys and values as the subset's + // metadata. The same host may appear in multiple subsets. + message LbSubsetSelector { repeated string keys = 1; } - repeated LbSubsetKeys subset_keys = 3; + repeated LbSubsetSelector subset_selectors = 3; } LbSubsetConfig lb_subset_config = 22; }