adamant-kite-43734
08/16/2023, 6:29 AMfast-bear-60513
08/16/2023, 7:15 AMK3S_URL
and K3S_TOKEN
environment variables to start k3s? This will make the k3s node join an existing cluster.
However I do recommend to use Rancher to deploy and manage clusters, it makes life way easier. You can use the quickstart documentation to easily bootstrap a cluster.victorious-dog-81595
08/16/2023, 8:25 AMfast-bear-60513
08/16/2023, 8:39 AM/var/lib/rancher
is mounted? It should be within the COS_PERSISTENT
partition, the elemental --reset
command should have created it.victorious-dog-81595
08/16/2023, 10:40 AMfast-bear-60513
08/16/2023, 1:44 PM--debug
flag to start k3s for more verbose logging.
And maybe double check the network settings? k3s uses 10.42.0.0/16
and 10.43.0.0/16
default ranges for pods and services, I wonder maybe some collision there with how the underlying machine is configured?victorious-dog-81595
08/17/2023, 9:21 AMvictorious-dog-81595
08/18/2023, 6:32 AMfast-bear-60513
08/18/2023, 7:19 AMfast-bear-60513
08/18/2023, 11:42 AMnative
or fuse-overlayfs
options for --snapshotter
This part of documentation is not up to date I fear and it may take some time before we can get to it.
For the moment I do recommend to bootstrap your k3s elemental nodes through Rancher, as it is the simplest and quickest way to do it: https://elemental.docs.rancher.com/quickstart-clivictorious-dog-81595
08/18/2023, 12:54 PM