I'm a bit unsure about this, because the limited volume with cloned git repos is mounted at /tmp/sandcastle, which is technically also a subdirectory of /tmp.

I am not sure either.
oc describe limitrange -n packit--prod-sandbox
Shows that the default limit for the storage in packit--prod-sandbox is 2Gi, I expect it to apply outside the mount point of our volume claim.

I am not sure either. oc describe limitrange -n packit--prod-sandbox Shows that the default limit for the storage in packit--prod-sandbox is 2Gi, I expect it to apply outside the mount point of our volume claim.

That's not what I'm unsure about, there is no limit apart from node physical disk size. I suppose you are talking about the 2GiB container image size limit, which is completely irrelevant here.

I am unsure about this too, in the cluster I can see limits.ephemeral-storage set to 10Gi, although I am not sure how exactly (if) this is being enforced, as I don't see per-pod limits for the ephermal storage. I would rather omit this part and not recommend this.

I have to admit I didn't try to dig deeper, I just did multiple practical tests creating large files and monitoring reported free space and I haven't found a node where there would be less than 50GiB of available space outside of /tmp/sandcastle. Even if there was 10GiB limit, it's still more than 3GiB and it would solve the issue for llvm-test-suite.

But if you prefer to omit this and rather increase the PVC in case more users report struggling to fit into 3GiB, it's fine by me.

ok, thanks for the details, then I would leave it just rewrite the second part of the sentence to something like , as it serves as a non-quota-restricted space for transient files.