outbound: remove required identity from HttpLogical
#683
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.
Presently, the proxy extracts the required identity from the
l5d-required-identity
header into theHttpLogical
target type whenit is present, and builds endpoint stacks which require that identity.
This was previously necessary because service discovery couldn't be
performed for pod IPs, only for authorities. However, this is no longer
the case, and we can now just use the identity returned by service
discovery for these stacks. This means the required identity can be
removed from the
HttpLogical
target, and identities inHttpEndpoint
targets are only provided by the destination metadata.
Fixes linkerd/linkerd2#5029