This message was deleted.

What is that error even from? That's not an error k3s or kubectl would give you. It mostly just looks like you haven't given something the path the the k3s admin kubeconfig?

Thanks @creamy-pencil-82913 agree can you please guide how to configure in path k3s admin kubeconfig.

Make sure your K3s.yaml matches your config file in ~/.kube/config and chmod 644 both files. also try export KUBECONFIG=/etc/rancher/k3s/k3s.yaml or where ever your config/k3s.yaml file is located...then your kubectl command should interact with k3s server if that doesn't work them restart your k3s server and run this command: export KUBECONFIG=/etc/rancher/k3s/k3s.yaml or where ever your config file is

Thanks Bryan, may I request you please share reference link/article that I can follow

Have you tried the k3s docs? https://rancher.com/docs/k3s/latest/en/cluster-access/

Thanks @creamy-pencil-82913 it helped. cheers mate

@creamy-pencil-82913 getting same error from worker node, so k3s.yaml is missing in worker node i only see this config.yaml.d registries.yaml