Oliver Gould
Oliver Gould
We've recently been running tests on the Linkerd proxy that exercise the load balancer in larger clusters (of 30+ endpoints). At the same time, I've been exploring the existing endpoint-weighting...
now that linkerd supports client certs, it should be pretty straightforward to instrument [spiffe](spiffe.io) support
There's a namerd script that is pinned to the `master` branch of `linkerd2-proxy-api` (which no longer exists): ``` namerd/iface/destination/src/main/resources/pull-destination-proto.sh:DESTINATION_PROTO=$(curl https://raw.githubusercontent.com/linkerd/linkerd2-proxy-api/master/proto/destination.proto) namerd/iface/destination/src/main/resources/pull-destination-proto.sh:NET_PROTO=$(curl https://raw.githubusercontent.com/linkerd/linkerd2-proxy-api/master/proto/net.proto) ``` This should be pinned to a specific...
We should add integration tests (i.e under namerd/storage/consul/src/integration) that exercise end-to-end interactions with a real consul server. Should verify dtab store functionality, as well as stats measurement.
Once #765 is addressed, it seems that we could transparently accept http1 requests on an h2 router (I.e. to upgrade them to h2 requests). Is there anything in Netty's codebase...
We should add integration tests (i.e under namer/consul/src/integration) that exercise end-to-end interactions with a real consul server. Ideally: 1. Build a consul namer from configuration yaml 2. register services into...
* [ ] create a new repo with copies of linkerd's `finagle` and `grpc` subprojects. The finagle project houses our h2 implementation and the grpc project has the protoc plugin,...
Currently, Netty's DefaultHttp2LocalFlowController provides no mechanism to configure the initial window size of the connection stream. Setting initial window size on the flow controller does nothing to change the connection...
From https://www.mnot.net/blog/2011/07/11/what_proxies_must_do > Proxies also need to be on the lookout for Content-Length headers that are duplicates, as well as ones that conflict with the use of Transfer-Encoding, and either...
Currently, linkerd propagates deadlines but does not act on them. Routers should expose configuration that causes them to use deadlines to enforce timeouts/nacking.