This message was deleted.
# elemental
a
This message was deleted.
f
Did you set the
K3S_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.
v
Hey @fast-bear-60513, I am not looking a way to join the cluster. The k3s cluster is installed on elemental, I am getting issues on the same cluster. Also, the kubelet.service is not available.
f
Are you using the latest stable version of k3s? (v1.27.4+k3s1) Also may you check if
/var/lib/rancher
is mounted? It should be within the
COS_PERSISTENT
partition, the
elemental --reset
command should have created it.
v
I am using v1.26.5+k3s1. and /var/lib/rancher is mounted.
f
Seems to be a problem with k3s configuration then. I would use the
--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?
v
I am still facing the same errors. I've checked network settings, no issue there.
hey, @fast-bear-60513, can you look into the configuration file https://rancher.github.io/elemental-toolkit/docs/tutorials/k3s_and_fleet_on_vanilla_image_example/#user-data-configuration-file if I am missing something or any changes? Do we have to mount overlay before this?
f
I'll try to reproduce asap
I can reproduce, indeed /var/lib/rancher is mounted as overlay, so as the logs suggest you can try either
native
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-cli
v
Thank you @fast-bear-60513 for your resppnse. will look into the approach you suggested.