Anyone else experiencing disconnects/timeouts when applying new custom resource definitions to a k3s single node cluster? I just wonder if it is normal. I can get around it by probing the kubernetes api URL until it works again.

sounds like you’re overloading the apiserver and it is either not responding until it can catch up, or you’re crashing the whole process and it’s restarting.

It's likely. I'm seeing a lot of disk activity when it happens too, but it's on my SBCs and some old Intel hardware too. It's propably just a case of slow i/o