K3s can reduce the footprint of a Kubernetes installation, but it does not remove the need to operate a cluster. Deploy one representative service with storage, ingress, secrets, and monitoring on the machines you plan to use. Then lose a node, restore state from backup, and perform an upgrade in a staging environment.
Record resource use and the time needed to recover. Edge or small-server constraints can make storage and network failure more important than initial installation speed. Adopt K3s when the team can run and repair it, not merely start it.