colossal-action-96650
12/27/2022, 3:44 PM2477 authentication.go:63] "Unable to authenticate the request" err="[invalid bearer token, [invalid bearer token, square/go-jose: error in cryptographic primitive]]"
And, they never show up in the output of kubectl get nodes
I’ve Googled that error and find many bug reports, posts, etc. but no definitive answer or solution. I’ve wiped out these new nodes and started fresh, but still get the same error.
Any advice would be appreciated.creamy-pencil-82913
12/27/2022, 8:11 PMcolossal-action-96650
12/27/2022, 8:37 PM/var/lib/rancher/k3s
which is the only place I'm aware of that contains the certificatescurl -sfL <https://get.k3s.io> | INSTALL_K3S_VERSION=v1.24.8+k3s1 INSTALL_K3S_EXEC="--disable traefik --disable servicelb --kube-controller-manager-arg bind-address=0.0.0.0 --kube-proxy-arg metrics-bind-address=0.0.0.0 --kube-scheduler-arg bind-address=0.0.0.0 --etcd-expose-metrics true --kubelet-arg containerd=/run/k3s/containerd/containerd.sock" K3S_TOKEN=[token] sh -s - server --server <https://10.3.14.2:6443>
is the latest version if the command I used to install K3s. I see server
and --server
in there, which would I need to eliminate. I was just trying to replicate the .service file flags as closely as I couldcreamy-pencil-82913
12/27/2022, 8:52 PMcolossal-action-96650
12/27/2022, 9:05 PMserver
flags? if so, which one?creamy-pencil-82913
12/28/2022, 12:46 AMserver
as in k3s server
which is a command… and then you have --server=<https://x:6443>
which is a flag that tells it where the existing server is.colossal-action-96650
12/28/2022, 3:25 PM