Oliver Gould

the way i've done this sort of thing in the past is passing in the config on stdin like: ``` ./genconfig.sh |./linkerd - ``` where genconfig.sh has something like: ```sh...

The port name could either be encoded in the name itself (as is done in kubernetes) or this could be made an explicit configuration option on the namer.

Can you share linkerd's metrics? (`:9990/admin/metrics.json?pretty=1`)

sorry, assume a dtab rule like `/svc/book => /$/inet/10.0.0.2/8080/api/published`

I suspect that finagle does most of this for us, but we should verify in e2e tests

This is a good idea. Though, I'd argue we don't need an onStart -- this should be a part of the plugin's Initializer -- and we should make Identifier implement...

Sorry for the radio silence on our end. We've been focused on a number of issues that touch finagle-h2, and moving this subproject out of this repo would add significant...

@kamilchm Yes. At the moment, we're focused on stabilizing the HTTP/2 codec for gRPC. Once the underling codec is ready for production, we'll pursue this and other enhancements.

@aryan9600 What do you think about omitting the `via` header for now? Users may not necessarily want to expose this information on requests so I'd like to be a bit...

If it's helpful context, we intentionally left this out of the initial scope so we could deliver something concrete for kubecon. It will definitely be an open topic afterwards ;)