https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# k3s
a
This message was deleted.
f
It shouldn't be talking to port 8080. But 6443. This usually means kubectl doesn't have access to the yaml conf.
m
Sorry, I don't quite understand the k3s configuration, which files should I modify?
f
Did you move the config to the location you specified?
And check the permissions
m
/etc/rancher/k3s/config.yaml
This is the position?
f
Or k3s.yaml. not next to a computer
Or is it in that directory you specified? If so try to export that path so kubectl knows where to look
m
I didn't use 'K3S_CONFIG_FILE' to specify it
Where should it go?
Even though I specify its location, it seems to be blank
f
export KUBECONFIG=/etc/rancher/k3s/k3s.yaml
Try running this
And then kubectl get nodes
m
Thank you very much for your answer. Are you the maintainer of the k3s community
f
Nope. Just someone who has stumbled around playing with k3s and happened to see your message 😄
m
Nice to meet you. What you met is a junior undergraduate student from China. There is an assignment about k3s
f
Neat!
Nice to meet you
The problem was kubectl was looking for a config file, couldn't find one and tried a basic setup.
m
yep, great article, thanks so much for your help
If you have any questions, please be sure to contact me, I will try my best to help you, about me, this is my GitHub https://github.com/cubxxw
💯 1
3 Views
Open in Slack
PreviousNext
Powered by