important-nightfall-75933
01/31/2023, 8:06 PMkubectl logs -n kube-system rke2-canal-m2ddv install-cni
says:
2023-01-31 19:52:05.466 [ERROR][1] cni-installer/<nil> <nil>: Unable to create token for CNI kubeconfig error=Post "https://10.43.0.1:443/api/v1/namespaces/kube-system/serviceaccounts/canal/token": dial tcp 10.43.0.1
:443: i/o timeoutI am using the
<https://get.rke2.io>
installer running on a fresh install of Ubuntu 20.04.4, and the only configuration I have done to is to configure NetworkManager to ignore CNI hosts. How can I resolve this issue?creamy-pencil-82913
01/31/2023, 8:07 PMimportant-nightfall-75933
01/31/2023, 8:09 PMcreamy-pencil-82913
01/31/2023, 8:11 PMimportant-nightfall-75933
01/31/2023, 8:12 PMcreamy-pencil-82913
01/31/2023, 8:12 PMimportant-nightfall-75933
01/31/2023, 8:14 PMnode-name
, node-external-ip
, and tls-san
creamy-pencil-82913
01/31/2023, 8:19 PMimportant-nightfall-75933
01/31/2023, 8:24 PMnode-external-ip
, it would use a NATed address that was causing problems for agents that weren't in the same network.
I set tls-san
because my intent was to set this up as a HA cluster with a proxy.creamy-pencil-82913
01/31/2023, 8:34 PMimportant-nightfall-75933
01/31/2023, 8:50 PMnode-external-ip
resolved this issue for me, and I am now able to start the RKE2 server successfully.