mirror of https://github.com/linkerd/linkerd2.git
b830efdad7
## What When the destination service returns a destination profile for an endpoint, indicate if the endpoint can receive opaque traffic. ## Why Closes #5400 ## How When translating a pod address to a destination profile, the destination service checks if the pod is controlled by any linkerd control plane. If it is, it can set a protocol hint where we indicate that it supports H2 and opaque traffic. If the pod supports opaque traffic, we need to get the port that it expects inbound traffic on. We do this by getting the proxy container and reading it's `LINKERD2_PROXY_INBOUND_LISTEN_ADDR` environment variable. If we successfully parse that into a port, we can set the opaque transport field in the destination profile. ## Testing A test has been added to the destination server where a pod has a `linkerd-proxy` container. We can expect the `OpaqueTransport` field to be set in the returned destination profile's protocol hint. Signed-off-by: Kevin Leimkuhler <kevin@kleimkuhler.com> |
||
|---|---|---|
| .. | ||
| api | ||
| cmd | ||
| gen | ||
| heartbeat | ||
| identity | ||
| k8s | ||
| proxy-injector | ||
| script/destination-client | ||
| sp-validator | ||
| tap | ||
| webhook | ||
| Dockerfile | ||