You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
K3s and other SUSe k8s distros accept the option --data-dir which allows a user to specify an alternative location for k3s data to be stored (replaces /var/lib/rancher)
Currently, when we connect new nodes to the cluster, we check the default location even if data-dir has been specified under k8s_distros.k3s.k3s_yaml.data-dir in the config file. this leads to the following error when attaching a new node:
> cat: /var/lib/rancher/k3s/server/node-token: No such file or directory
Describe alternatives you've considered, if any
This can sort-of be worked around by specifying a new storage class for local-path provisioned that points tot he desired directory but that will still leave the core k3s components installed to /var/lib/rancher which can cause unexpected disk-pressure issues.
The text was updated successfully, but these errors were encountered:
Describe the feature you'd like, and why
K3s and other SUSe k8s distros accept the option
--data-dir
which allows a user to specify an alternative location for k3s data to be stored (replaces /var/lib/rancher)Currently, when we connect new nodes to the cluster, we check the default location even if
data-dir
has been specified underk8s_distros.k3s.k3s_yaml.data-dir
in the config file. this leads to the following error when attaching a new node:> cat: /var/lib/rancher/k3s/server/node-token: No such file or directory
Describe alternatives you've considered, if any
This can sort-of be worked around by specifying a new storage class for local-path provisioned that points tot he desired directory but that will still leave the core k3s components installed to
/var/lib/rancher
which can cause unexpected disk-pressure issues.The text was updated successfully, but these errors were encountered: