Add support for service-mirror selectors #4795
Merged
+145
−450
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #4481
We add support for the source cluster to now specify which services from the target cluster should be exported by using a
label selector rather than looking for the
mirror.linkerd.io/gateway
andmirror.linkerd.io/gateway-ns
annotations. Further context for this change is described in linkerd/rfc#31The
Link
resource spec now has aselector
field which contains a label selector. All services in the target cluster which match this selector will be mirrored. This selector can be set by using the--selector
flag to themulticluster link
command and follows the same format as the--selector
flag does in kubectl. The selector can alternatively be set by editing the Link resource directly. If the selector flag tomulticluster link
is left unspecified, it defaults to the selector:mirror.linkerd.io/exported
.Some example usage: