https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# k3s
a
This message was deleted.
c
… why are you overriding the kubelet’s client CA?
n
I found on stackoverflow that this could be the way to connect to the server IP via https. Anyway, now I'm running the client as follows with the same result: curl -sfL https://get.k3s.io | INSTALL_K3S_EXEC="agent --server https://SERVER_PUBLIC_IP:6443 --token TOKEN --node-name agent" sh -s -
I can see the agent "ready" but when I deploy a pod, I got the same mesage and the status pending forever
c
no. don’t copy paste random stuff from stack overflow. k3s always uses tls between agents and server.
✅ 1
make sure that you have all the correct ports open between your nodes. Make sure that you have --node-external-ip set to the public IP on your server.
n
open ports: 80, 22, 6443, 443, 9500-9503, 9808, 51820-51821
--node-external-ip
should be set in k3s.service? I can't see it
with --node-external-ip I got the same result
c
Server should be started with --node-external-ip=YOURIP so it knows to advertise the external IP to the agent. Normally nodes would all connect to each other via internal IP, why are you using the external IP?
n
the docs says:
Copy code
curl -sfL <https://get.k3s.io> | K3S_URL=<https://k3s.example.com> sh -s - agent --token mypassword
K3S_URL seems like a public thing
what is your advice to run the agent? what should be the command?
c
no, K3S_URL should be the address or hostname of the server. 
<https://SERVER:6443>
- if they are both on the same network, then use its internal IP or hostname.
n
running this: curl -sfL https://get.k3s.io | INSTALL_K3S_EXEC="agent --server https://internal_ip:6443 --token token --node-name agent" sh -s - I got the same message and result
354 Views
Open in Slack
PreviousNext
Powered by