Shashank Ram
Shashank Ram
> This PR does 2 things: > > 1. Pushes message coalescing from a global message broker to a per-proxy goroutine. Could you measure the performance impact at scale with...
> There's a lot of requests to provide performance numbers. I get the desire to do that, however we unfortunately lack good tooling to test this. I'll try to add...
Note that the rea > > > There's a lot of requests to provide performance numbers. I get the desire to do that, however we unfortunately lack good tooling to...
Previously, we used FluentBit for this. You can run it as a sidecar to stream logs to an external data store. The FluentBit configuration can be tweaked to parse and...
> Yeah, the advantage of the OTel approach is that it's not specific to fluentbit and it occurs directly in the Envoy proxy, so you prevent the Yet-Another-Sidecar problem That...
@nlamirault thanks for contributing. Could you open up an issue describing the need for this change so we can discuss further. Thanks
> Note from an offline convo I had with @steeling: when backporting for a patch, perhaps we should use a staging branch of sorts so that all of the proposed...
> Oh I didn't mean to maintain a long-lived staging branch; just once we've decided to create a patch for a backport, we make PRs into a holding area so...
> /remove-kind bug Please search other issues and read docs. Then post the info requested in the issue-template. Its not even clear if your service type is NodePort or LoadBalancer...