paullegranddc
paullegranddc
Sure, added a QA section
@katiehockman Which milestone should I put on the PR?
For context, this is a request from @kevingosse . He want to use the crashtracker in situations were the it doesn't have access to the library variables, so the goal...
I have been playing around to write a more efficient string interner. https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=e0d9de41fe195efc6a3c72b0ed39efe8 It keeps the interned strings in a contiguous array of memory, which should reduce memory pressure.
After discussion with @cijothomas we will hold on merging the breaking changes in this PR until after the next release since there are currently no breaking changes in the changelog.
I added a goroutine pool to forward the requests. This allows to limit the number of inflight requests as well as the number of inflight bytes
/merge
Closing an reopening because of the rebase
Hey @clamoriniere We've changed our approach to compute the max resources pods are using and setting our limit/request to that on init containers. For QoS Guaranteed, since limits == request...
> My only worry is that we don't always set resources values anymore, and it can block pod creation is some cases Not sure this is an acceptable answer, but...