This message was deleted.
# generala
adamant-kite-43734
08/21/2025, 2:24 AMThis message was deleted.
c
creamy-pencil-82913
08/21/2025, 2:40 AMThe admin kubeconfig always points at localhost. This is normal.
creamy-pencil-82913
08/21/2025, 2:40 AMDid you remember to pass the token as well when joining the second node? Are the correct ports open?
c
creamy-autumn-72353
08/21/2025, 2:41 AMThe open ports are: 22, 80, 443, 6443
And yeah, the token is passed with
K3S_TOKENcreamy-autumn-72353
08/21/2025, 2:41 AMThe only other env var is
INSTALL_K3S_VERSION: "v1.29.15+k3s1"c
creamy-pencil-82913
08/21/2025, 2:41 AMThat is not the correct set of ports. Please read the docs.
creamy-pencil-82913
08/21/2025, 2:42 AMc
creamy-autumn-72353
08/21/2025, 2:43 AMAh yeah, I was looking for this page
creamy-autumn-72353
08/21/2025, 2:43 AMI stumbled across it a couple of years ago but forgot where it was
creamy-autumn-72353
08/21/2025, 2:43 AMThanks
creamy-autumn-72353
08/21/2025, 2:43 AMI'll give that a shot now
creamy-autumn-72353
08/21/2025, 2:55 AMThat moved things forward.
I've run into this though
Copy code
level=fatal msg="starting kubernetes: preparing server: failed to bootstrap cluster data: Get \"<https://192.168.88.212:6443/v1-k3s/server-bootstrap>\": tls: failed to verify certificate: x509: certificate signed by unknown authority"creamy-autumn-72353
08/21/2025, 2:55 AMIf I recall there's a config param to skip certificate validation, right?
creamy-autumn-72353
08/21/2025, 3:27 AMWeird
I recreated the cluster and the second server node successfully registered this time
creamy-autumn-72353
08/21/2025, 3:27 AMI guess I must've done something slightly different last time
2 Views