https://rancher.com/ logo
Join Slack
Powered by
Hi I am running into issues when trying to add a 2...
# k3s
h
Hi I am running into issues when trying to add a 2nd server to my cluster. I think the issue has to do with the automatic proxy setup. I'm trying to setup an air-gapped solution and do not need a proxy to reach the internet. At the moment it is not cut off from the internet, but will be in the future. 
x.x.x.x
is the IP I am connecting to from the outside.
Copy code
msg="Connecting to proxy" url="<wss://x.x.x.x:6443/v1-k3s/connect>" 
msg="Failed to connect to proxy. Empty dialer response" error="dial tcp x.x.x.x:6443: connect: connection refused"                                                                                                
msg="Remotedialer proxy error; reconecting..." error="dial tcp x.x.x.x:6443: connect: connection refused" url="<wss://x.x.x.x:6443/v1-k3s/connect>"
I tried setting 
--node-ip
with the network I need the nodes to communicate over, but no luck.
b
I'd check that you connect to 6443 from the new node. Maybe there's a route or firewall issue.
h
Sadly that is not the issue, but definitely a good first place to check.
b
Oh? What's the output of nmap from the second node?
h
I can successfully telnet to the port
b
From your machine and the second node?
Oh, it's trying to use the kube api port as a proxy
that's not right
h
Yes believe because the kubelet picks the interface with the default route.
b
It should probably join over the backend IP and not the other
And not use a proxy at all
c
This isn't a proxy like you're thinking of.
This is a websocket proxy that is used to tunnel traffic between nodes.
Make sure you can make a request with curl to the IP and port shown in that message
h
And if I can't? Can I change it with node-ip or external-node-ip?
c
correct
👍 1
68 Views
Open in Slack
PreviousNext
Powered by