Florian Kasper

Hey @M00nF1sh thanks for your input. I fear this is exactly what I thought was supposed to fix it. But thinking about it: if the server does all of this:...

I was just wondering whether this should be solved at a lower level - that's why I also opened an issue on k/k. This is not something just limited to...

 I've also drawn up a convenient picture detailling the issue further - the big, organge box is where things are happening decoupled from one another.

@BrianKopp we've thought about running a sidecar, which provides a statically linked binary to a common - in mem - volume, that the main container could use as preStop. I...

Oh I was not talking about processing the sigterm in the sidecar. If you read closely I only spoke about providing the binary ;) For our use case even a...

we've actually started sharding our services across multiple aws accounts/eks clusters, just to lower the number of pending/throttled API requests and to increase the speed at which each controller can...

in my case unsetting the `DISPLAY` and setting browser to `/usr/bin/true` as suggested by @riponbanik solved the issue - on WSL

we've already added metrics and can't really see this issue anymore. It was just really obvious when you initialize a nodejs application and fetch something from AWS immediately right after...

@pingles sorry for the late response. This got somewhat lost on our table. Since my last comment we've updated to v3.4, but are still facing problems when rolling out both...

Facing a very similar issue here. After some digging I found https://github.com/fluent/fluent-bit/pull/8738 which might have caused this issue. Although I am not sure how to use the newly introduced event...