This message was deleted.
# generala
adamant-kite-43734
08/16/2022, 10:02 PMThis message was deleted.
t
tall-school-18125
08/16/2022, 10:29 PMWhat command did you use to join the agent node? In order for the agent to connect, it needs the token to be passed in as described in this comment https://github.com/k3s-io/k3s/issues/1523#issuecomment-602098986
n
narrow-action-54485
08/16/2022, 10:33 PMI used:
Copy code
curl -sfL <https://get.k3s.io> | K3S_URL=https://$K3S_URL:6443 K3S_TOKEN=$K3S_TOKEN sh -s -b
brainy-postman-1566
08/16/2022, 11:09 PMpretty sure the value of K3S_TOKEN should just be :
K3S_TOKEN=$K3S_TOKEN when referencing an env var...
brainy-postman-1566
08/16/2022, 11:10 PMand of course always a good idea to ensure it resolves to the value you expect using echo $K3S_TOKEN in shell.
n
narrow-action-54485
08/16/2022, 11:13 PMthat's what I have: K3S_TOKEN=$K3S_TOKEN
I think I got it, but in hacky way. This is on AWS EC2. I had the SG open up all traffic between the two nodes. However, something was still missing. After I opened all traffic from anywhere, it worked. Which is horrible practice of course, so I need to figure out which protocol/ports was missing specifically
b
brainy-postman-1566
08/16/2022, 11:23 PMah misread that. cool glad you figured it out 👍
t
tall-school-18125
08/17/2022, 6:36 AMThe port requirements for k3s are here https://rancher.com/docs/k3s/latest/en/installation/installation-requirements/#networking
👍 1
46 Views