Workaround

quick note if you dont want spammy EndpointSliceUpdate logs, just delete the local-path-provisioner but obviously that would break your pvcs in a vanilla kind cluster

The issue

On any kube-proxy running in kind, the local-path-provisioner for rancher makes a bunch of noise

I0907 13:28:05.246094       1 config.go:260] Calling handler.OnEndpointSliceUpdate
I0907 13:28:

I'm think s/--quite/--quiet/ was the intention with Spacefile.sh#L441 and its associated consumers?

Reading a long README is painfully annoying, especially when the installation procedure is far down the README. At least the table of contents is there, but it's still really hard to access because the README is overwhelmingly long.

I suggest creating a website (distrobox.github.io I guess) so we can have a good place to document without overwhelming a newcomer.

Add an example workflow in the examples/gradle/ folder that exemplifies how to make use of Popper to create a CI pipeline for java projects that use gradle as their build system. The image used by the workflow can be the official one.

Steps to reproduce:

1. Create a recording
2. Let it run for some time, then archive it
3. Request a report for the archived recording and note how long it takes to receive a response
4. Download the archived recording to your local machine
5. Re-request the same report again and note that the response time is much shorter, due to the caching. This can be verified by checking the Cryostat lo