This message was deleted.
# rke2a
adamant-kite-43734
08/17/2023, 5:38 PMThis message was deleted.
c
creamy-pencil-82913
08/17/2023, 6:05 PMIt's trying to contact the existing cluster member on ipv6, not rancher. If you don't want ipv6 on your nodes you should disable it at the OS level.
c
creamy-autumn-87994
08/17/2023, 6:08 PMThe template has ipv6 disabled in sysctl.conf. I deleted the server line referencing ipv6 in
/etc/rancher/rke2/config.yaml.d/50-rancher.ymlc
creamy-pencil-82913
08/17/2023, 6:09 PMIf you delete the server line from the config then the server creates new cluster instead of having it join an existing cluster. That's probably not what you wanted.
creamy-pencil-82913
08/17/2023, 6:10 PMI would check that your sysctls are actually being used, if the nodes have ipv6 addresses on their interfaces then it would seem that they are not.
c
creamy-autumn-87994
08/17/2023, 6:10 PMI don’t see any ipv6 listed with
ip ac
creamy-pencil-82913
08/17/2023, 6:10 PMOn the new nodes, or the existing nodes?
c
creamy-autumn-87994
08/17/2023, 6:11 PMOn the new. Ohh I’ll check existing
c
creamy-pencil-82913
08/17/2023, 6:11 PMWhat do you see in
kubectl get node -o widecreamy-pencil-82913
08/17/2023, 6:11 PMYes, it's pulling the primary address off existing nodes, because the new nodes need to contact an existing node to join. If the primary ip is ipv6, it'll try to join over ipv6.
c
creamy-autumn-87994
08/17/2023, 6:12 PMAh okay, ty!
22 Views