What should I expect the k3s cluster to react when an agent fails due to some network/hardware failure?

[BeaverBytes]

Environment setup
Cluster configuration:

• 1 server node
• 2 agent nodes

Discussion
Hey guys, so I'm a bit new to the setting up a high availability kubernetes cluster. When I first created my K3s cluster, I wanted to test out how workloads would be handled in K3s when one of my agent fails. What I was expecting was that the server node would notice the agent node to be down and have the Deployment workload be transferred to an available agent quickly, but it took a surprisingly long time (~5-7 minutes) for the workload to be transferred to another agent. I'm wondering if anyone has any insight on why it would this long and if there is a way to reduce the network time for transferring the workload?

[brandond]

You might see the thread at #1264 where some users attempted to tune the various default monitoring and eviction thresholds to reduce the time it takes to get pods rescheduled to other nodes. Note that changing these thresholds from their defaults may cause additional load and/or other undesired behavior; test with care before rolling out any of these changes in a production environment.