By default, K3s uses a config file for etcd that can be found at $etcdconf. The config file contains client-transport-security: which has fields that have the peer cert and peer key files. No manual remediation needed.
By default, K3s uses a config file for etcd that can be found at $etcdconf. client-cert-auth is set to true. No manual remediation needed.
By default, K3s starts Etcd without this flag. It is set to false by default.
By default, K3s starts Etcd with a config file found here, $etcdconf. The config file contains peer-transport-security: which has fields that have the peer cert and peer key files.
By default, K3s uses a config file for etcd that can be found at $etcdconf. The config file contains peer-transport-security: which has client-cert-auth set to true. No manual remediation needed.
By default, K3s uses a config file for etcd that can be found at $etcdconf. Within the file, it does not contain the peer-auto-tls field. No manual remediation needed.
By default, K3s uses a config file for etcd that can be found at $etcdconf and the trusted-ca-file parameters in it are set to unique values specific to etcd. No manual remediation needed.