k3s server create 100% CPU load

[allnightlong]

Environmental Info:
K3s Version:
k3s -v
k3s version v1.30.6+k3s1 (1829eaa)
go version go1.22.8

Node(s) CPU architecture, OS, and Version:
Linux ***-master 6.8.0-48-generic #48-Ubuntu SMP PREEMPT_DYNAMIC Fri Sep 27 14:04:52 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Cluster Configuration:
1 server
6 agents

Describe the bug:
100% CPU usage of k3s processes on master node. Can't diagnose and find out root of the problem.
HTOP screenshot

NewRelic CPU usage for 3 days screenshot

Steps To Reproduce:
I'm not sure exactly, how to reproduce the problem. My application creates a lot of short-living kube jobs.
Could it be the cleanup problem?

As 3 days graph suggests, the CPU load increases day-by-day (while the application is having the same load), so k3s finally arrives at the point, where CPU load is unbearable.

I've tried to run:

k3s-killall.sh
systemctl start k3s

from this topic #6095 (comment), but it never helped.

So I've ended up reinstalling the whole cluster on my new machine, just to find myself in the same situation 5 days after.

Expected behavior:
CPU load shouldn't reach over 100%

Actual behavior:
CPU load reaches 100%, and as a result it takes too long for kubernetes to launch pods, so the jobs falls out of the deadline.

Additional context / logs:
I can provide any necessary logs on the request