Hi, using k3s version 1.24.11 we have limited the TLS cipher suites of etcd and kubelet to exclude some suites that were being flagged in security scans. We are using the suits golang "crypto/tls" package provides but excluding the problematic ones from it. Since the change everything appears to be working fine however we see that a new error periodically (though not frequently) appears in k3s service journal.

11116 upgradeaware.go:440] Error proxying data from backend to client: write tcp 10.100.73.98:6443->10.244.0.22:39048: write: broken pipe

From some googling it appears that it related to communication between kube-api-server and kubelet, we tried setting the same cipher suits in kube-api-server but still getting the same error. So we are trying to figure out whether this is a critical issue, as everything appears to be working fine, and also if you have any idea how we can resolve said issue?