k3s server crashes abruptly when approximately 300 requests are sent in a span of 60 seconds (client QPS is 5 and bursty limit is 10) about k3s

[brandond]

This is a crash DEEP in a core go garbage collection function. I do not believe that this is something we can address here in K3s. The fact that you see this under load, and the resulting stack is in the go runtime garbage collection routine suggests that it is running out of memory and trying to force GC, and that is somehow running into memory corruption while doing so ( ref golang/go#57550 (comment)).

How much memory does this node have? How much of that is available to k3s, when your workload is present? Have you tried profiling k3s while updating your application?