This message was deleted.

K3s agents don't run the control plane components, so any kubectl requests would just be forwarded onto a server node.

Perhaps you can copy

/etc/rancher/k3s/k3s.yaml

file from server node to your agent node, and rename it to

~/.kube/config

, so that you can use

kubectl

command to manage your cluster.