This message was deleted.

Nope, sure can't. Just make sure k3s gets restarted periodically (you're patching or replacing your nodes, right) and you'll be fine.

Thanks. Ok i see. The reason is that this is mostly run as a fire and forget single node VM. The reason why its kubernetes is that its an existing k8s app that we run in the cloud but should also be runnable in onprem in some cases. Then it was much simpler to us k3s as a runtime then to mess with docker compose or similar since we already had the helm package and everything. Using secrets and configmaps etc.