Flynn
Flynn
I've run into this with both [Emissary-ingress](https://github.com/emissary-ingress/emissary) and [Linkerd](https://linkerd.io/). The Emissary-ingress case is simplest to describe, so I'll do that first: like NGINX as described by @kate-osborn, Emissary only supports...
This seems like a good idea, let's do it. 👍
FTR I'd vote for adding copyright -- Envoy Gateway is already Apache-2 licensed, which is pretty permissive.
(Don't we now alternate 3PM PST and 8AM PST every other week?)
Yeah, this is a good shout. Where would you think it most useful to have this information?
@robscott, on the mesh front, Linkerd actually doesn't support the fixed-number-of-retries concept. Instead there's a retry budget: if your retry budget is e.g. 20%, then as long as not more...
Linkerd configures retries at the route, too, FWIW...
Thinking it over, I think defaulting to enabling the extended features for most (all?) profiles and having a `--core-only` makes more sense.
Hmmmmmmm. @rgs1, do you have a minimal config to hand to reproduce this? There are some subtleties with TCPMappings; I want to make sure I'm looking at the scenario you're...
I think this has long since been tackled. 🙂 /close