Specifies how matching should be done.
Supported values are:
MATCH_ANY: At least one of the Labels specified in the
matcher should match the metadata presented by xDS client.
MATCH_ALL: The metadata presented by the xDS client should
contain all of the labels specified here.
The selection is determined based on the best match. For
example, suppose there are three EndpointPolicy
resources P1, P2 and P3 and if P1 has a the matcher as
MATCH_ANY <A:1, B:1>, P2 has MATCH_ALL <A:1,B:1>, and P3 has
MATCH_ALL <A:1,B:1,C:1>.
If a client with label <A:1> connects, the config from P1
will be selected.
If a client with label <A:1,B:1> connects, the config from P2
will be selected.
If a client with label <A:1,B:1,C:1> connects, the config
from P3 will be selected.
If there is more than one best match, (for example, if a
config P4 with selector <A:1,D:1> exists and if a client with
label <A:1,B:1,D:1> connects), an error will be thrown.
Specifies how matching should be done.
Supported values are:
MATCH_ANY: At least one of the Labels specified in the
matcher should match the metadata presented by xDS client.
MATCH_ALL: The metadata presented by the xDS client should
contain all of the labels specified here.
The selection is determined based on the best match. For
example, suppose there are three EndpointPolicy
resources P1, P2 and P3 and if P1 has a the matcher as
MATCH_ANY <A:1, B:1>, P2 has MATCH_ALL <A:1,B:1>, and P3 has
MATCH_ALL <A:1,B:1,C:1>.
If a client with label <A:1> connects, the config from P1
will be selected.
If a client with label <A:1,B:1> connects, the config from P2
will be selected.
If a client with label <A:1,B:1,C:1> connects, the config
from P3 will be selected.
If there is more than one best match, (for example, if a
config P4 with selector <A:1,D:1> exists and if a client with
label <A:1,B:1,D:1> connects), an error will be thrown.
The list of label value pairs that must match labels in the
provided metadata based on filterMatchCriteria This list can
have at most 64 entries. The list can be empty if the match
criteria is MATCH_ANY, to specify a wildcard match (i.e this
matches any client).
The list of label value pairs that must match labels in the
provided metadata based on filterMatchCriteria This list can
have at most 64 entries. The list can be empty if the match
criteria is MATCH_ANY, to specify a wildcard match (i.e this
matches any client).
The list of label value pairs that must match labels in the
provided metadata based on filterMatchCriteria This list can
have at most 64 entries. The list can be empty if the match
criteria is MATCH_ANY, to specify a wildcard match (i.e this
matches any client).
The list of label value pairs that must match labels in the
provided metadata based on filterMatchCriteria This list can
have at most 64 entries. The list can be empty if the match
criteria is MATCH_ANY, to specify a wildcard match (i.e this
matches any client).
The list of label value pairs that must match labels in the
provided metadata based on filterMatchCriteria This list can
have at most 64 entries. The list can be empty if the match
criteria is MATCH_ANY, to specify a wildcard match (i.e this
matches any client).
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-02-06 UTC."],[],[]]
