This message was deleted.

full disclosure - I do not use k3s but maybe this can help identify a pod (or 2) if you reboot the node how much memory does it start out using and then perhaps monitor with

kubectl top pod -A

to determine which pod is the culprit ? and review its logs

After a reboot: Memory(bytes): 869Mi (10%) (kubectl top nodes)